Getting Started & Migration
How do I safely test a migrated workflow prior to full production cutover?
A reliable way to test a migrated workflow before full cutover is to use isolated shadow testing with limited test traffic. Route a small volume of non-critical test traffic to the Catalyst-hosted workflow, compare outputs against your existing engine without altering live user traffic, and validate consistency across all workflow steps. Keep in mind that shadow testing does not capture in-flight work state changes, so it is not suitable for long-running ongoing executions.
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.
