Getting Started & Migration
After migration, how can I use parallel runs or shadowing to compare the new durable agent's decisions against the old agent's without affecting production?
Run both old and newly durable agents side by side with the same production inputs for a representative period. Divert the durable agent’s outputs to a shadow sink, then compare decision logs for parity. This technique detects divergence without risking side effects. A caveat: differences in execution order or timing due to replay can cause false positives, so focus comparison on logical outcomes rather than intermediate API call sequences.
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.