Getting Started & Migration
Should I move in-flight work during Catalyst migration?
Your decision to move in-flight work during a Catalyst migration depends on your specific timeline and workflow requirements. If you can complete all pending work before the official cutover, avoid transitioning in-flight tasks to reduce overall complexity; if immediate cutover is necessary, use Catalyst’s built-in tools to resume interrupted runs after the switch. Note that containment is not prevention, so plan for potential partial failures during the broader migration transition period.
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.
