This is why we purge cache from CI after a deploy[0], and other places when our users publish a story, etc.

That said, the edge-caching being how it is, it's possible to run into some race-conditions where the cache has been purged but not propagated to the edge network, and if visited too soon, the stale version might end up back into the cache.

[0]:

  curl --fail --output "/dev/null" --silent --show-error -X POST "https://api.cloudflare.com/client/v4/zones/{our_zone_id}/purge_cache" \
    -H "Authorization: Bearer $CLOUDFLARE_CACHE_PURGE_API_TOKEN" -H "Content-Type: application/json" \
    --data '{"hosts": ["instorier.com", "www.instorier.com"]}'