Enabled Only Means It Was Saved, Not That It Ran

Enabled only means it was saved, not that it ran


The rule remains in the list where you placed it. Its switch shows Active, the panel is green, and the URL still opens the previous page. Nothing in the interface appears wrong, because nothing there is. Active means the setting was approved and is cleared to run; it says nothing about whether any call ever got through to it.



Matching is where most of an afternoon goes, and one behaviour accounts for more of it than the rest together. A wildcard is checked against the entire address, the query string included, so a pattern that does not end open will miss any request bearing parameters. That is exactly what happens when you add something to defeat the browser cache: the cache-buster defeats the pattern instead, the page loads normally, and you assume the rule is broken. Operators differ in whether they care about case, which turns a path typed from a design document into a rule that matches nothing. Bulk lists act the other way round and disregard parameters completely, but subpath and subdomain coverage stay disabled unless enabled, and a list that no rule activates does nothing at all.



That discrepancy is the bulk of the assessment. Saved and ran are two distinct states, and the dashboard can only show the first one. Between a visitor and your setting there is the proxy mode of the record, the order in which products are evaluated, and sometimes a region in an account that is not yours. Until you know which handler saw the request first, arguing about the rule itself is guesswork. The solution comes from a request, not from another glance at the configuration.


Your request may never reach your region


There are three ways to sit outside your own zone, and they look identical from the inside. A record left unproxied gives visitors the origin address, so they connect directly to it and your edge settings are never checked. A zone whose nameservers were never switched at the registrar remains unresolved: everything you configured is real, and none of it is live. And a hostname onboarded to a platform that fronts it with a zone of its own may leave that platform responding first, with your configuration a note nobody reads. A temporary rule on a path nothing handles, asked for once with a plain request, distinguishes all three in about a minute.



The full write-up, with every step and what each answer resolves: workers free plan cpu limit



The order is what rescues the evening: did it arrive, did the pattern match it, did something respond sooner, and are you reading a plain query rather than a browser tab that may be showing you yesterday. Each question is answered once, and the one that returns incorrect is the one to repair.