Can you explain how to debug persistent CloudFront CDN caching issues where invalidation requests fail to purge stale API responses originating from our backend load balancers?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Can you explain how to debug persistent CloudFront CDN caching issues where invalidation requests fail to purge stale API responses originating from our backend load balancers?
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (2)
Classes come from the query-classifier (a local Laya model). 2 of 2 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
AWS CloudFront troubleshooting invalidation stale content cache key origin cache headers X-Cache Age documentation OBSERVED | Google ↗ AI Mode ↗ | — | Reason | — | — | 1x of 1 | |
AWS CloudFront invalidation status completed cache behavior TTL cache policy origin response headers documentation OBSERVED | Google ↗ AI Mode ↗ | — | Reason | — | — | 1x of 1 |