Cache

Route/authoring/cache PreviewHosted planhosted

Cache — "Presets, expert rules, trace and scoped purge for this environment." — records the edge cache policy for the project's production lane. The page says, at the top, that no managed delivery tier is attached yet: the rules do not shape response headers and a purge evicts nothing, while the policy, the trace and the purge record are real. A project without a managed site reads "This project has no managed site, so there is no environment to configure cache policy for."

Tab	What it does
Presets	Four cards — Standard, Aggressive, Bypass, Personalized — each printing its TTLs and stale settings, intent, rationale and "Not safe with" list, with a Current tag. Clicking a card applies it at once. Bypass is an incident mode ("Requires an expiry. This is an incident mode, not a configuration.") and expires after four hours
Rules	Expert rules ("No expert rules on this lane. The preset below decides every route.") and Preset rules, listed read-only
Trace	A Method, Host and Path, evaluated against the recorded policy: eligibility, the winning rule, TTL, bypass, the cache key, and a Rules considered table (Rule, Outcome, Why). A trace is an evaluation, not a replay
Purge	What to purge — a release, tag, prefix, host or URL — with a scope and a required Reason. Estimate scope shows the sample routes it would touch; Purge… opens the Purge cache impact sheet. Host, prefix and release scopes must be typed back to confirm; URL and tag scopes take a checkbox
History	Every purge on the lane, including refusals and "No delivery tier was attached, so nothing was evicted."

Expert rules are reserved to the Platform operator role: "Expert cache rules are available to the Platform operator role. Presets, trace and purge remain available."