Getting Started & Migration
What’s the rollback approach if a migrated durable agent shows unexpected behavior in production?
Keep the original agent path deployed in parallel, using feature flags to switch traffic back quickly. Catalyst’s durable execution state is isolated, so rolling back means routing new requests to the legacy system while preserving in-flight workflow state for inspection. Be aware that in-flight durable workflows will still run to completion under the migrated logic unless terminated explicitly.
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.