// AI Platform Drift

Cloudflare Workflows adds per-workflow concurrency limits

Cloudflare developer changelog · published 2026-11-13 19:47 UTC
WORTH KNOWING VERIFY_ONLY LIMITSAPI
WHAT CHANGEDCloudflare Workflows now supports setting a concurrency limit on individual workflows via a concurrency.limit parameter in the workflows binding configuration. The limit caps how many instances of a single workflow can run simultaneously. Instances above the limit are queued and start automatically as running instances finish. The limit must be a positive integer and cannot exceed the account-level limit (100 on Workers Free, 50,000 on Workers Paid). Requires Wrangler 4.127.0 or above.
WHY IT MATTERSWithout per-workflow limits, one high-volume workflow can consume an account's entire concurrency quota, starving other workflows. The new limit also protects downstream systems—databases or third-party APIs—that degrade or reject requests past a certain number of concurrent connections. However, if you deploy without concurrency.limit in your configuration after setting it once, the limit is removed and the workflow reverts to using the full account limit.
WHAT TO DOIf you need to protect a backend system or distribute load across workflows, add concurrency.limit to your workflows binding configuration and upgrade to Wrangler 4.127.0 or above. If you set a limit, ensure concurrency.limit is present in every subsequent deploy to prevent it from being removed.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Workflows, Workers - Set a concurrency limit for each Workflow
+https://developers.cloudflare.com/changelog/post/2026-11-10-per-workflow-concurrency-limits/
+Tue, 10 Nov 2026 00:00:00 GMT
+
+You can now set a concurrency limit on an individual Workflow to cap how many of its instances run at the same time. Use it to protect a database or third-party API that slows down or rejects requests past a certain number of concurrent connections, or to distribute load more evenly across your Workflows so that one high-volume Workflow does not use all of your account's concurrency.
+For example, to allow only 10 instances of a Workflow to run at a time, set concurrency.limit on its workflows binding and redeploy:
+{
+"workflows": [
+{
+"name": "my-workflow",
+"binding": "MY_WORKFLOW",
+"class_name": "MyWorkflow",
+"concurrency": {
+"limit": 10,
+},
+},
+],
+}[[workflows]]
+name = "my-workflow"
+binding = "MY_WORKFLOW"
+class_name = "MyWorkflow"
+
+[workflows.concurrency]
+limit = 10
+You can also set concurrency on a Workflow declared in exports, or with exports.workflow() in @cloudflare/config.
+Instances above the limit are not rejected. They are queued and start automatically as running instances finish or move to the waiting state.
+The limit must be a positive integer, and cannot be higher than your account's concurrency limit (100 on Workers Free, 50,000 on Workers Paid). Lowering the limit does not stop instances that are already running. Workflows without a concurrency limit can still use up to your account's full concurrency limit.
+CautionSet concurrency.limit in your configuration on every deploy. If you deploy without it, the Workflow's concurrency limit is removed.
+Per-Workflow concurrency limits require Wrangler 4.127.0 or above.
+For more information, refer to Concurrency limits.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningNew per-Workflow concurrency control feature with configuration requirements and account limits affects deployment and execution behavior.
signalsnew feature announcement · new configuration parameter introduced (concurrency.limit) · account-level limit constraint documented (100 Free / 50,000 Paid) · tool version requirement (Wrangler 4.127.0+) · deployment behavior change (limit removal on redeploy without config) · future date (2026-11-10)
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)