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 ¹	10 seconds	30 seconds of active CPU time
Duration (wall clock) per step ¹	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 ²	64 characters	64 characters
Maximum `step.sleep` duration	365 days (1 year) ³	365 days (1 year) ³
Maximum steps per Workflow ⁴	1024 ³	1024 ³
Maximum Workflow executions	100,000 per day shared with Workers daily limit	Unlimited
Concurrent Workflow instances (executions) per account	25	100 ³
Maximum number of queued instances	10,000 ³	100,000 ³
Retention limit for completed Workflow state	3 days	30 days ⁵
Maximum length of a Workflow ID ²	64 characters	64 characters

A Workflow instance can run forever, as long as each step does not take more than the CPU time limit and the maximum number of steps per Workflow is not reached. ↩ ↩²
Match pattern: ^[a-zA-Z0-9_][a-zA-Z0-9-_]*$ ↩ ↩²
This limit will be reviewed and revised during the open beta for Workflows. Follow the Workflows changelog for updates. ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷
step.sleep do not count towards the max. steps limit ↩
Workflow state and logs will be retained for 3 days on the Workers Free plan and for 7 days on the Workers Paid plan. ↩

Footnotes