Getting Started & Migration
What is a safe rollback strategy if a migrated durable agent behaves unexpectedly in production?
Keep the original agent deployment live and use a feature flag to instantly switch traffic back. Catalyst stores state compatible with the original path, so in-flight executions can be failed gracefully and the old agent can pick up from a known checkpoint. This avoids losing work if the durable version encounters unexpected behavior. Boundary: State format changes between versions may prevent seamless handoff; test rollback on a subset first.
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.