Getting Started & Migration
How do I design the local development environment to simulate realistic partial failures, so I can see durable execution recovering state?
Introduce an in-process fault injector that raises exceptions at specific step boundaries or causes transient I/O errors. Run the agent with a local state store and observe how Catalyst replays from the last checkpoint after each failure. This approach verifies your step idempotency under controlled conditions. Note that this simulates crashes but cannot replicate all production failure modes like network partitions or node outages, which may affect external service interactions.
Was this article helpful?
Your feedback helps improve Diagrid's FAQ experience.
Keep reading
More Diagrid FAQ articles
- Getting Started & Migration
What does a minimal but realistic durable agent look like when I first run Catalyst locally?
A realistic durable agent prototype that progresses from a call to an LLM through a conditional action to an API, illustrating automatic state persistence.
- Getting Started & Migration
How do I iterate quickly on durable agent logic without deploying to a shared cluster?
Use a local Dapr sidecar to execute and debug agent workflows, enabling a fast edit-run-debug cycle without remote dependencies.
- Getting Started & Migration
My agent is already built with LangChain/LlamaIndex. Can I add durable execution without a rewrite?
Wrap an existing agent’s entry point in a Catalyst workflow to gain durability without modifying framework internals, then progressively refactor.