A rollback fixes one region but cached errors persist elsewhere

What to change

Ask the hosting owner to distinguish restored origin content from cached public responses. Record the affected addresses and any available cache evidence, then apply the site's controlled invalidation approach if appropriate. Test through fresh external requests and a returning session rather than relying only on the restoration operator's browser. The incident remains partly unresolved until the agreed public sample receives the corrected behaviour or the remaining scope is clearly communicated.

A worked example

Illustrative example

Illustrative test: Independent fresh requests receive the restored page instead of the earlier cached failure.

How to check the result

The public recovery evidence covers the delivery layer visitors actually use.

A mistake to avoid

Repeatedly redeploying identical files may not address the cache condition.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordConfirm the restored origin or deployment response where supported.Compare representative public cached responses for the same routes.Recheck after the approved cache correction or expiry plan.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.