What is cached for this tenant, what depends on what, and whether invalidations are arriving.
How this page works
Four layers: raw chunks (L0) fetched from the CMS, the final page (L1) returned to the frontend engine, a page transformer's composed page, and the assembly manifest recording how a page's blocks were sourced.
To debug "the page didn't update after publish": find the page's L1 key in the table, open Depends on to see its chunks, then check the invalidation log for the webhook that should have cleared them. The webhook tile at the top shows whether any webhooks are arriving at all.
- Last received
- never
- Last 24 h
- 0 received · 0 failed
No publish events arrived in the last 24 hours. If content was published, check the webhook configuration in Contentstack.
A hit means the Substation answered from its cache; a miss means it had to fetch or build the answer again. A low hit ratio on a busy group is where caching is not helping.
| Cache group | Hits | Misses | Hit ratio |
|---|---|---|---|
| Config: connections | 0 | 2 | 0% |
| Key | Group | Hits | Misses | Hit ratio |
|---|---|---|---|---|
config_connections:all | Config: connections | 0 | 2 | 0% |
Raw chunks (L0): content fetched from the CMS, one entry per reference. Dependents lists what a chunk (L0) feeds into; Depends on lists the chunks a page-level entry was built from.
Nothing cached in this layer
Either nothing has been fetched for this tenant yet, or the entries have expired.
Showing every tenant. Show this tenant only
No invalidation log entries match.
Danger zone — flush this tenant's cache
Clears every layer for all at once (optionally the CDN too). The next request re-fetches everything from the CMS.