Interesting, I never really knew setting Action to "Managed challenge" would be equivalent to skipping all the remaining rules and this is coming from someone who is managing multiple Enterprise Cloudflare accounts for the past couple of years. Thanks.
> In other way this seems to be intended behavior even though Cloudflare dashboard is straight lying to you by saying that Block rule will execute after Challenge action:
> Above statement is not true, as the rule will never be evaluated after “Force bot detection” rule.
Actually what you are saying is not true because the rule is evaluated after your previous rule just like it says, only as long as it was not a terminating action which is documented. Just because you created two conflicting rules in the incorrect order does not mean that their UI text is incorrect or lying to you.
I think "as long as it was not a terminating action" is crucial here. The way how Cloudflare dashboard is designed right now may put you in false sense of security by implying that all rules will be evaluated one after another. In my opinion, they could do a better job UI-wise on highlighting, that a terminating action will result in skipping all subsequent rules.
It's a failing on the part of Cloudflare to have used rules so many times and not realize this important detail.
It's not expressed anywhere in the UI, so at some point someone really just said "well the user will figure it out."
I like Cloudflare's products, the their vibe for all of their documentation is "well the user will figure it out."
Interesting, I never really knew setting Action to "Managed challenge" would be equivalent to skipping all the remaining rules and this is coming from someone who is managing multiple Enterprise Cloudflare accounts for the past couple of years. Thanks.
What is the most stressful part of your job? Crazy customers or CEOs?
> In other way this seems to be intended behavior even though Cloudflare dashboard is straight lying to you by saying that Block rule will execute after Challenge action:
> Above statement is not true, as the rule will never be evaluated after “Force bot detection” rule.
Actually what you are saying is not true because the rule is evaluated after your previous rule just like it says, only as long as it was not a terminating action which is documented. Just because you created two conflicting rules in the incorrect order does not mean that their UI text is incorrect or lying to you.
I think "as long as it was not a terminating action" is crucial here. The way how Cloudflare dashboard is designed right now may put you in false sense of security by implying that all rules will be evaluated one after another. In my opinion, they could do a better job UI-wise on highlighting, that a terminating action will result in skipping all subsequent rules.