Cloudflare Workflows Schedules

Gotchas

• 100K workflow invocations/day

  Free plan shares the Workers daily request quota of 100,000 invocations per day across all Workers and Workflows on the account.

• 100 new instances/second creation rate

  Free plan is capped at creating 100 new Workflow instances per second; exceeding this returns HTTP 429.

• 10ms CPU time per step

  Each Workflow step is limited to 10ms of active CPU time on the Free plan, versus 30 seconds (configurable to 5 minutes) on Paid — severely restricting compute-heavy steps.

• 100 concurrent running instances

  Only 100 Workflow instances can be actively running simultaneously on the Free plan; Paid allows 50,000.

• 1,024 steps per workflow (vs 10K–25K paid)

  Free plan caps each Workflow instance at 1,024 steps; Paid plan defaults to 10,000 and is configurable up to 25,000.

• 3-day state retention

  Completed and errored Workflow instance state is retained for only 3 days on Free, versus 30 days on Paid.

• 1GB workflow state storage

  Free plan includes 1GB of persistent Workflow state storage; instances will throw errors when this limit is reached.

• 100 Worker scripts per account

  Free plan allows only 100 total Worker/Workflow script definitions per account, versus 500 on Paid.

• 50 subrequests per step (external)

  Each Workflow step on Free is limited to 50 external subrequests and 1,000 subrequests to Cloudflare services; Paid defaults to 10,000 and can be raised to 10 million.

• 100MB persisted state per instance

  Maximum state that can be persisted per single Workflow instance is 100MB on Free vs 1GB on Paid.

• No cron concurrency budget

  Paid plan grants cron-triggered Workflow instances a dedicated one-hour concurrency budget per firing outside normal concurrency slots; Free plan has no such budget.

• 3MB max script size

  Workers Free limits each Worker/Workflow script to 3MB; Paid allows up to 10MB.