Limits

Limits that apply to authoring, deploying, and running Workflows are detailed below.

Many limits are inherited from those applied to Workers scripts and as documented in the Workers limits documentation.

Feature	Workers Free	Workers Paid
Workflow class definitions per script	3MB max script size per Worker size limits	10MB max script size per Worker size limits
Total scripts per account	100	500 (shared with Worker script limits
Compute time per step 1	10 seconds	30 seconds (default) / configurable to 5 minutes of active CPU time
Duration (wall clock) per step 1	Unlimited	Unlimited - for example, waiting on network I/O calls or querying a database
Maximum persisted state per step	1MiB (2^20 bytes)	1MiB (2^20 bytes)
Maximum event payload size	1MiB (2^20 bytes)	1MiB (2^20 bytes)
Maximum state that can be persisted per Workflow instance	100MB	1GB
Maximum length of a Workflow ID 2	64 characters	64 characters
Maximum step.sleep duration	365 days (1 year) 3	365 days (1 year) 3
Maximum steps per Workflow 4	1024 3	1024 3
Maximum Workflow executions	100,000 per day shared with Workers daily limit	Unlimited
Concurrent Workflow instances (executions) per account	25	4500 3
Maximum Workflow instance creation rate	100 per 10 seconds 35	100 per 10 seconds 35
Maximum number of queued instances	10,000 3	100,000 3
Retention limit for completed Workflow state	3 days	30 days 6
Maximum length of a Workflow ID 2	64 characters	64 characters

Need a higher limit?

To request an adjustment to a limit, complete the Limit Increase Request Form ↗. If the limit can be increased, Cloudflare will contact you with next steps.

Increasing Workflow CPU limits

Workflows are Worker scripts, and share the same per invocation CPU limits as any Workers do. Note that CPU time is active processing time: not time spent waiting on network requests, storage calls, or other general I/O, which don't count towards your CPU time or Workflows compute consumption.

By default, the maximum CPU time per Workflow invocation is set to 30 seconds, but can be increased for all invocations associated with a Workflow definition by setting limits.cpu_ms in your Wrangler configuration:

wrangler.jsonc

{
  // ...rest of your configuration...
  "limits": {
    "cpu_ms": 300000, // 300,000 milliseconds = 5 minutes
  },
  // ...rest of your configuration...
}

wrangler.toml

[limits]
cpu_ms = 300_000

To learn more about CPU time and limits, review the Workers documentation.