Cloudflare Workflows adds per-Workflow concurrency limits with auto-queuing
dinasaur_404 · x · 2026-11-11
Cloudflare shipped a Workflows update letting developers set a concurrency limit on individual Workflows, capping how many instances run at once to protect databases or third-party APIs and to prevent one high-volume Workflow from hogging the account's entire concurrency budget.
Key details:
- Set concurrency.limit on the workflow binding (e.g. limit of 10); also configurable via exports or exports.workflow()
- Instances above the limit aren't rejected — they queue and start automatically as running instances finish or enter the waiting state
- The limit must be a positive integer and can't exceed the account limit (100 on Workers Free, 50,000 on Paid); lowering it doesn't stop already-running instances
- Requires Wrangler 4.127.0+
More from coding & agent
- HydraDB builds a unified knowledge graph to give AI agents accurate context — vaibhavbetter · 2026-11-11
- Reddit Users Compare Notes on GLM-5.3-flash's Random Coding Mistakes — JustinHoMi · 2026-11-11
- Dev fine-tunes Qwen3-1.7B into a 1.83GB GLB 3D asset coder that runs on CPU — ConfidentDinner6648 · 2026-11-11
- Solo dev shares 20k-word workflow: Opus 5.5 + Seedance 2.5 for 4 viral product videos — dotey · 2026-11-11
- CodeGraph turns codebases into Neo4j graphs so agents can do dependency-aware refactoring — JeremyCMorgan · 2026-11-11
- Primitive imagines guardian agents that enforce team decisions infrastructure-wide — daniel_mac8 · 2026-11-11