Getting Started & Migration
How do I manage in-flight work during Catalyst migration?
Prioritize resolving in-flight work before full cutover to avoid conflicting state between platforms. Route new work to Catalyst incrementally, and flag existing in-flight tasks to finish on the original engine or migrate their state safely. Use observability tools to track both workload streams without mixing execution contexts. Note that observability data alone is not a full audit record, so cross-check state consistency for critical tasks.
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.