Workflows - Rollback support now available in Workflows
Cloudflare Workflows has introduced saga-style rollback support, enabling developers to attach compensating logic directly to each step.do() call. This feature addresses the challenge of cleaning up partial work in multi-step operations that touch external systems, such as inventory reservations, payment authorization, ticket creation, or infrastructure provisioning. Instead of writing all cleanup logic in a top-level catch block, developers can now keep each compensating action next to the step it undoes, improving code organization and maintainability. When a workflow instance fails, rollback handlers execute in reverse step-start order, ensuring that resources are released or actions undone in the correct sequence. Each rollback handler can be configured with its own retry and timeout settings, providing fine-grained control over failure recovery. Workflows now also exposes rollback outcomes in instance status responses, and analytics emit rollback lifecycle events, making it easier to distinguish between a forward execution failure and a rollback failure when debugging production workflows. This feature is particularly useful for developers building reliable, multi-step workflows that interact with external APIs or services.
Simplifies error recovery by keeping cleanup logic next to each step, reducing boilerplate and debugging complexity.