Durable Execution
How does Diagrid Catalyst handle side effects like payment or email API calls that must be exactly-once?
Catalyst does not guarantee exactly-once for external API calls. It provides at-least-once delivery by persisting workflow state and replaying deterministic steps after crashes. For payment or email APIs, you must implement idempotency keys or reconciliation. Design each side-effecting activity to be safely retryable. Catalyst handles recovery, but idempotency is your application's concern.
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.