Skip to content

Commit 379b5bf

Browse files
Workers Cache purge uses free tier limits (#32898)
Co-authored-by: ask-bonk[bot] <ask-bonk[bot]@users.noreply.github.com> Co-authored-by: irvinebroque <irvinebroque@users.noreply.github.com>
1 parent 088a6ed commit 379b5bf

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

src/content/docs/workers/cache/purge.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -368,4 +368,4 @@ On failure, each error in `errors` carries a numeric `code` and a human-readable
368368

369369
## Rate limits
370370

371-
`purge()` uses the same rate-limiting system as Cloudflare's zone purge API. For the rate limits that apply to your account's plan, refer to [Availability and limits](/cache/how-to/purge-cache/#availability-and-limits). When the purge is rate-limited, `success` is `false` and `errors` contains an entry describing the rejection.
371+
`purge()` uses the same rate-limiting system as Cloudflare's zone purge API. However, because Workers Caching is associated with the Worker rather than the zone, Workers Cache always uses the **Free tier limits** described in [Availability and limits](/cache/how-to/purge-cache/#availability-and-limits), regardless of your account or zone plan. When the purge is rate-limited, `success` is `false` and `errors` contains an entry describing the rejection.

0 commit comments

Comments
 (0)