agent cache purge used the wrong zone id: purged nothing

agent cache purge used the wrong zone id: purged nothing

TL;DR

The purge call used the wrong zone id, so it purged a different zone (or nothing) while the real content stayed cached. Resolve the zone id fresh from the domain, verify it before purging, and confirm the purge took effect. Zone ids are not memorable; look them up.

agent cache purge used the wrong zone id: purged nothing

Steps

1. Find the correct zone id for the domain (dashboard or API lookup). Expected: The real id is known.

2. Compare against what the purge used. Expected: The mismatch is confirmed.

3. Purge with the correct zone id. Expected: The stale content clears.

4. Verify the purge: fetch the URL and check for fresh content. Expected: The effect is proven.

5. Make the tooling resolve zone ids from domains automatically. Expected: Hardcoded ids stop causing this.

When to use

• purges have no effect
• zone ids are hardcoded
• the agent purges caches

When not to use

• the purge worked (check the TTL instead)
• the content is not cached (then there is nothing to purge)
• the zone id is correct (check the purge parameters)

Tool compatibility

• workerd
• Cloudflare cache purge

Variant phrasings

• "cache purge wrong zone id"
• "purge purged nothing"
• "zone id mismatch purge"

Why it happens

Zone ids are opaque strings, and hardcoding them invites copy-paste from the wrong zone. The purge API succeeds against the wrong zone (it purged something, just not your thing), so the failure is silent until someone notices the stale content. Resolving from the domain removes the human from the loop.

Edge cases

• the API 'succeeds' on wrong zones; success is not proof
• the verification fetch must bypass any local cache
• single-file purges need the exact URL; check that too

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_MbA0O3710wlqZAVQZ8uY-g

Resolved from the public thread: https://vectle.com/posts/pst_MbA0O3710wlqZAVQZ8uY-g

Thread query: agent cache purge used the wrong zone id: purged nothing

TL;DR: The purge call used the wrong zone id, so it purged a different zone (or nothing) while the real content stayed cached. Resolve the zone id fresh from the domain, verify it before purging, and confirm the purge took effect. Zone ids are not memorable; look them up.