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 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 state that can be persisted per Workflow instance | 100MB | 1GB |
Maximum step.sleep duration | 365 days (1 year) 2 | 365 days (1 year) 2 |
| Maximum steps per Workflow | 512 2 | 512 2 |
| Maximum Workflow executions | 100,000 per day shared with Workers daily limit | Unlimited |
| Concurrent Workflow instances (executions) | 25 | 100 2 |
| Retention limit for completed Workflow state | 3 days | 30 days 3 |
| Maximum length of a Workflow ID 4 | 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. ↩ ↩2
-
This limit will be reviewed and revised during the open beta for Workflows. Follow the Workflows changelog for updates. ↩ ↩2 ↩3 ↩4 ↩5
-
Workflow state and logs will be retained for 3 days on the Workers Free plan and for 7 days on the Workers Paid plan. ↩
-
Match pattern:
^[a-zA-Z0-9_][a-zA-Z0-9-_]*$↩