Today, due to high traffic, I noticed that one of my page rules for caching disabled itself. Checking the audit log in my account, I noticed that the page rule was disabled by the user IP address “127.0.0.1”, which I assume indicates that this was CF-internal.
I couldn’t find anything regarding this on here or in documentation, is this just something that can happen? Did any error on my side cause CF to turn the page rule off?
I don’t use WARP, any adtech or Zero Trust, and never logged into anything else like WP plugins with my CF account, sorry. It uses hardware-backed 2FA.
This makes me suspect of rules in general - I probably should not be relying on them for caching.
However, the “Always Online” toggle was never turned on from its off (and known) position, and previously we never updated from the legacy Always Online to the new Archive.org-based one.
Still trying to figure out if 127.0.0.1 is indeed the Cloudflare network (is it?), why “Cloudflare” wasn’t the user performing this logged action.