# Published event update not showing: diagnostic record

Use this worksheet for **one exact public URL and locale at a time**. The example is a corrected entry time that editors approved and published, but some attendees still see the prior value. The goal is to locate the stale layer before changing cache settings or purging content.

## 1. Confirm the approved fact and release

| Observation | Value, evidence, owner and time zone |
|---|---|
| Exact public URL and locale, including query string if relevant | [ ] |
| Approved new value and source-of-truth reference | [ ] |
| Old value being seen and where | [ ] |
| CMS publish event, version or deployment identifier | [ ] |
| Page, API response, asset or third-party embed containing the value | [ ] |
| Event owner and urgency of attendee impact | [ ] |

## 2. Compare layers before changing them

| Surface | Exact request/device/network | New or old value? | Useful response evidence | Responsible team |
|---|---|---|---|---|
| Authorized origin or preview of published release | [ ] | [ ] | Version / timestamp | [ ] |
| Public page on unaffected network | [ ] | [ ] | URL, response Date, Cache-Control, Age or vendor cache header if present | [ ] |
| Public page on affected network/device | [ ] | [ ] | Same fields; screenshot and time | [ ] |
| Browser or service-worker path, if applicable | [ ] | [ ] | Fresh profile versus normal profile; registered worker if known | [ ] |
| Linked registration or external checkout | [ ] | [ ] | Exact destination and displayed value | [ ] |
| Search result or social preview, if reported | [ ] | [ ] | Surface and crawl/preview time | [ ] |

Different pages, locale prefixes, query strings, image URLs and embedded services may have different cache behavior. A fresh browser profile is a diagnostic comparison, not proof that every attendee receives the update. A search snippet is another surface, not necessarily the live page.

## 3. Choose a scoped action and verify

| Decision | Record |
|---|---|
| Layer supported by evidence: unpublished origin / browser / service worker / CDN / embed / other | [ ] |
| Proposed change and exact URL or cache key scope | [ ] |
| Authorized owner and rollback or follow-up plan | [ ] |
| Change request, execution status and provider receipt | [ ] |
| Recheck from affected and unaffected networks, with time | [ ] |
| Event page, registration entry and ticket link all show intended value | [ ] |
| Attendee/support communication owner if public misinformation persisted | [ ] |

Avoid a blanket purge unless the relevant provider owner has determined it is needed. CDN invalidation may not remove a copy already held by a browser or another intermediary. Keep the observation record with the publication or incident ticket.