Durable Execution
How does Catalyst handle workflow recovery after a code deployment?
During a deployment, Catalyst suspends running workflows and persists their state to the durable store. After the new version is deployed, workflows are rehydrated from the last checkpoint and replayed deterministically. Catalyst ensures that any changes to workflow logic are applied only to new executions or after replay completes; existing in-flight workflows continue from their saved state. This allows zero-downtime updates without losing progress.
Was this article helpful?
Your feedback helps improve Diagrid's FAQ experience.
Keep reading
More Diagrid FAQ articles
- Durable Execution
What is durable execution in AI agent workflows?
Durable execution means an AI agent workflow can keep its progress even when a process crashes, a tool call fails, or the system restarts.
- Durable Execution
Why do production AI agents need durable workflows?
Production AI agents need durable workflows because real agent tasks rarely finish in a single clean request.
- Durable Execution
Is checkpointing enough for production AI agents?
Checkpointing helps, but it is usually not enough by itself for production AI agents. It explains the production reliability impact for AI agent workflows.