Skip to content

Conversation

@nenizera
Copy link
Contributor

Hello team,

Summary

Can we warn customers here about potential impacts on their origin server and their application performance due to purge everything?

Thanks!

Can we warn customers here about potential impacts on their origin server and their application performance due to purge everything?
@nenizera nenizera requested review from a team and angelampcosta as code owners May 28, 2025 17:50
@hyperlint-ai
Copy link
Contributor

hyperlint-ai bot commented May 28, 2025

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.


PR Change Summary

Added a cautionary note regarding the potential impacts of purging everything on origin server performance.

  • Introduced a warning about the effects of purging everything on application performance.
  • Highlighted that a cache response marked as EXPIRED may lead to execution delays.
  • Emphasized the need for caution when performing a purge everything operation.

Modified Files

  • src/content/docs/cache/how-to/purge-cache/purge-everything.mdx

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

@github-actions github-actions bot added the product:cache Issues or PRs related to Cache label May 28, 2025
@angelampcosta
Copy link
Contributor

He think this note is not necessary, since the page already states "Purging everything instantly clears all resources from your CDN cache in all Cloudflare data centers. Each new request for a purged resource returns to your origin server to validate the resource. If Cloudflare cannot validate the resource, Cloudflare fetches the latest version from the origin server and replaces the cached version."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product:cache Issues or PRs related to Cache size/xs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants