Durable Execution
How does Catalyst secure workflow state during persistence and replay?
Workflow state is encrypted at rest in the durable store using customer-managed or platform-managed keys. During replay, state is decrypted in memory only for the duration of execution. Catalyst enforces workload identity-based access control, so only authorized agent runners can read or write state. Audit logs track all state accesses. For air-gapped deployments, encryption keys can be stored locally, and no state leaves the environment.
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.