changes how workflows track state internally. Instead of updating records in place, every state change is now stored as an event, and current state is reconstructed by replaying the log. This release also adds support for provider-executed tools and higher throughput.Workflow 4.1 Beta is a persistence pattern where state changes are stored as a sequence of events rather than by updating records in place. Instead of storing "this run is completed," the system stores "run_created, then run_started, then run_completed" and reconstructs the current state by replaying those events.Event sourcing In Workflow 4.1, runs, steps, and hooks are no longer mutable database records.

They're materializations of an append-only event log. Each event captures a timestamp and context, and the runtime derives current state by processing events in order. This architecture makes workflows more reliable in three ways: For a deeper look at the event model, including state machine diagrams for run, step, and hook lifecycles, see the .Event Sourcing documentation Learn more about or with your first workflow.Workflowget started Read more What event sourcing means for workflows Other updates : If a queue…