How can I rewrite my Cloudflare worker routing logic to stay well under the strict worker request limits while handling a sudden Black Friday traffic surge happening right this second.
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
How can I rewrite my Cloudflare worker routing logic to stay well under the strict worker request limits while handling a sudden Black Friday traffic surge happening right this second.
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 2 queries…
Searches and sources
ChatGPT2 real searches · gpt-6
Cloudflare Workers limits requests subrequests CPU duration current documentation 2026 Google ↗
Cloudflare Workers traffic spikes caching routing performance best practices official docs Google ↗
- Limits · developers.cloudflare.com
- Workers are no longer limited to 1000 subrequests · developers.cloudflare.com
- Workers Cache · developers.cloudflare.com
- Cache · developers.cloudflare.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Cloudflare Workers limits requests subrequests CPU duration current documentation 2026 OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
Cloudflare Workers traffic spikes caching routing performance best practices official docs OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |