Getting Started & Migration
When I roll back a migrated durable agent, what verification steps confirm that no in-flight executions are still partially persisted in the new state store before I fully decommission the old system?
Query the Catalyst state store for outstanding workflow instances after disabling new invocations, ensuring no partial executions remain before decommissioning. Drain active runs by stopping ingress, then inspect the store with management APIs to list incomplete workflows, and wait for them to finish or safe-terminate. Incomplete workflows with human-in-the-loop steps may require appropriate signaling before termination; verify that task queues are empty. Forced cancellation can risk inconsistent side-effects if steps are not idempotent.
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.