Agent InfrastructureAutomated source watch

Workflows - Default instance retention for new Workflows on Workers Paid is seven days

Cloudflare Workflows changelog published Workflows - Default instance retention for new Workflows on Workers Paid is seven days. Workflows created on or after September 10, 2026, on the Workers Paid plan retain completed and errored instance state for seven days by default (previously 30 days). The seven day default helps to reduce storage costs by default.…

Human read

Why this signal matters

Cloudflare Workflows changelog published Workflows - Default instance retention for new Workflows on Workers Paid is seven days. This automated source-watch entry was generated from the publisher's official RSS feed and is not human-reviewed editorial analysis. Source excerpt: Workflows created on or after September 10, 2026, on the Workers Paid plan retain completed and errored instance state for seven days by default (previously 30 days). The seven day default helps to reduce storage costs by default. The maximum retention limit remains 30 days. The retention period for existing Workflows is unchanged. The Workers Free plan retains its three-day default and limit. To set the retention period for a Workflow instance, specify successRetention , errorRetention , or both: const instance = await env. MY WORKFLOW . create ({ retention: { successRetention: "2 days" , errorRetention: "30 days" , }, }); const instance = await env. MY WORKFLOW . create ({ retention: { successRetention: "2 days" , errorRetention: "30 days" , }, }); You can also set the retention period per Workflow and per instance in the Cloudflare dashboard ↗︎ . For retention details, refer to…

Agent parse

Actionable summary

Treat Workflows - Default instance retention for new Workflows on Workers Paid is seven days as an official publication signal. Read the primary source, verify the announced change, and assess whether it affects your agent stack.

Agent usefulness
75/100
Confidence
90%
Canonical data
JSON + Markdown
Next actions

What builders should check

  • Read the original Cloudflare Workflows changelog article before relying on this summary.
  • Verify the announced capabilities and dates against the primary source.
  • Assess whether the change affects your agent stack or evaluation plan.
Classification

Tags and routing

cloudflareworkflowschangelog
Related signals

Continue the thread