Data changed somewhere else
The problem
An import job or a CMS changes data without going through your GraphQL API, so no mutation passes the cache and nothing tells it what changed.
With GraphPilot
Name the key in a Surrogate-Key header on your origin's response, call the purge API or gpilot purge from a webhook or a cron job, or purge in the Cockpit. A purge can name a surrogate key, a cache key, a query hash or everything.
Docs: The purge API ↗Transcript
Sometimes data changes without passing through GraphPilot: a nightly import, a CMS, a price feed.
No mutation comes through, so nothing tells the cache, and the old answers stay until they expire.
When a write does pass through, your origin can name extra keys in a Surrogate-Key header on its response.
From a webhook or a cron job, call the purge API, or run gpilot purge.
Or press Purge in the Cockpit.
Purge by surrogate key, by cache key, by query, or everything. Hard, or soft, so readers keep the old answer while a fresh one is fetched.
Every purge is listed in the Cockpit, automatic or by hand, with who sent it.
Cleared for takeoff
Start on Glider (Free).
No credit card, no commitment.
Prefer to talk first? Book a call