Workflows - Workflows now supports delay functions when retrying
Cloudflare Workflows changelog published Workflows - Workflows now supports delay functions when retrying. With Workflows , you can configure built-in retry behavior for each step. Previously, you could configure step retries with fixed delay durations, such as seconds, minutes, or hours, and backoff strategies such as constant , linear , or exponential .…
Why this signal matters
Cloudflare Workflows changelog published Workflows - Workflows now supports delay functions when retrying. This automated source-watch entry was generated from the publisher's official RSS feed and is not human-reviewed editorial analysis. Source excerpt: With Workflows , you can configure built-in retry behavior for each step. Previously, you could configure step retries with fixed delay durations, such as seconds, minutes, or hours, and backoff strategies such as constant , linear , or exponential . Step retries now support dynamic delay functions. Instead of choosing only a base delay and backoff strategy, pass a function to retries.delay and calculate the next delay from the failed attempt and thrown error. This is useful when retries should depend on the failure. Your Workflow may need to wait longer after a rate-limit error, but retry sooner after a short network failure. The delay function can also accommodate provider guidance if, for example, a downstream API returns a Retry-After value in its error messaging. await step. do ( "sync customer" , { retries: { limit: 5 , delay : ({ ctx , error }) = { if (error.message. includes (…
Actionable summary
Treat Workflows - Workflows now supports delay functions when retrying as an official publication signal. Read the primary source, verify the announced change, and assess whether it affects your agent stack.
- Agent usefulness
- 80/100
- Confidence
- 90%
- Canonical data
- JSON + Markdown
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.