Getting Started & Migration
What steps should I take to verify my first migrated workflow is production-ready?
Your first critical, necessary step to ready a migrated workflow for production is confirming it aligns with your existing production workload behaviors. Run limited, targeted side-by-side test traffic, compare detailed execution traces and core measurable business outcomes, and verify error handling and retry logic align with your specified business requirements. Note that durable execution does not provide exactly-once delivery semantics, so plan ahead proactively for duplicate run checks.
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.
