Workflow 4.1 Beta: Event-sourced architecture
By Steven Van ·
The update also boosts workflow queue throughput and adds provider-executed search tools for AI agents.
Workflow 4.1 Beta changes how Vercel's Workflow SDK tracks state internally. Runs, steps, and hooks are no longer mutable database records: every state change is stored as an event, and current state is reconstructed by replaying that append-only log, with each event carrying its own timestamp and context.
Vercel says the event-sourced model makes workflows more reliable in three ways:
- Self-healing: if a queue message is lost or a race condition occurs, replaying the workflow route detects the missing state and re-enqueues the necessary messages automatically. Old runs needed manual intervention to recover from queue downtime.
- Complete audit trail: the event log can be replayed to see the exact sequence that led to any state, which makes debugging distributed workflows easier.
- Consistency: because events are append-only, a partial failure during a write can't leave an entity in an inconsistent state.
Other updates
- The workflow queue now processes many thousands of steps per second, running multiple steps in parallel when dependencies allow.
- @workflow/ai now supports provider-executed tools such as Google Search and WebSearch, which run on the model provider's infrastructure rather than in the workflow itself.
- A new @workflow/nest package adds build support for NestJS, handling dependency injection so workflows integrate with existing NestJS services.
Details on the run, step, and hook state machines are in the Workflow documentation.
Vercel
The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.
View Vercel →