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.…
原始内容为英文;当前页面提供中文导航与来源说明,具体事实请以原文为准。
为什么值得关注
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…
可执行摘要
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 实用度
- 75/100
- 可信度
- 90%
- 机器格式
- JSON + Markdown
开发者应核对什么
- 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.