Cache status, health check and worker updates
On this page
Once Super Cache is deployed, Settings → AjaxPress → Cache shows a status panel instead of the setup screen.
The status panel
| Item | Meaning |
|---|---|
| Your domain | The site the cache is running on |
| Pause caching | A switch that stops edge caching at once, without disconnecting. See Pause, disconnect or remove |
| pages on the edge | How many pages AjaxPress has cached in the Global layer |
| Last synced | When AjaxPress last sent its settings (such as your exclusions) to Cloudflare |
| Global layer active | A globally replicated copy of your pages is in use, for fast first visits in every region |
| Edge worker v… | The version of the Worker running on Cloudflare |
Below it are Cache all pages, the purge box, Cache health and Pages to never cache.
Check cache health
Click Check cache health. Your browser requests your home page and a few recent posts and pages, and reads Cloudflare’s answer for each one:
| Result | Meaning |
|---|---|
| HIT | Served from Cloudflare’s cache nearest to you. This is what you want |
| HIT-KV | Served from the Global layer. Also a cached page |
| STALE | A cached copy was served while a fresh one is fetched in the background |
| MISS | Fetched from your server, and now cached for next time |
| BYPASS | Deliberately not cached: the page is excluded, caching is paused, or the request can’t be cached |
| UNKNOWN | The request didn’t go through the cache at all. See Super Cache problems |
A page is a MISS the first time it’s requested, and a HIT after that, so a fresh cache shows mostly MISSes. Browse a few pages, or run Cache all pages, then click Check again to see the rate climb. Hide results clears the list.
Checking while logged in? That’s fine. The health check asks for the pages the way a logged-out visitor would see them.
Always MISS?
If pages stay MISS after several checks, see Super Cache problems. The usual causes are a plugin that sets a cookie on every page, and a DNS record that isn’t proxied.
Worker updates
The edge worker updates itself when a new version of AjaxPress Pro includes changes to it. You don’t need to do anything.
If an update can’t be installed (for example, while Cloudflare has an outage), AjaxPress retries a few times over the next few hours. If it still fails, a notice appears: “The edge worker could not be updated after several attempts.” Your site keeps being cached by the worker that’s already installed, so nothing breaks. Click Update worker now to try again.
If updating keeps failing, disconnect and connect again, which reinstalls the worker from scratch.