Getting Started & Migration
How can I safely migrate in-flight workflow work without disruption?
You can safely migrate in-flight workflow work without disruption by following structured, validated operational steps. First pause or carefully checkpoint ongoing work to avoid data inconsistencies, map existing workflow state to the durable execution model, validate state transfer with sample in-progress workflow runs, then test full resumption of work after migration. Keep in mind observability tools for durable execution are not audit records, so retain original state logs as needed.
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.
