Workflow 4.1 Beta: Event Sourcing Architecture

Workflow 4.1 Beta introduces an event sourcing architecture that stores every change as an event instead of directly updating state. Now runs, steps, and hooks reconstruct their current state through an immutable append-only event log.

This architecture improves workflow reliability in three ways.

• Self-healing: When queue message loss or race conditions occur, log replay detects and automatically recovers missing state.
• Complete audit trail: The event log allows the exact sequence that led to a given state to be reproduced, making it easier to debug distributed workflows.
• Consistency: Since events can only be appended, partial failures during write operations don't cause data inconsistency, and the event log serves as the single source of truth.

Other key updates include the following.

• Improved throughput: Queue system optimization and parallel execution support to handle thousands of steps per second.
• Provider-executed tools: Support for tools that run on model providers' infrastructure, such as Google Search.
• NestJS support: Integration with existing NestJS services via the @workflow/nest package.
• Resource management: Automatic resource cleanup via support for TC39's using declaration.