Getting Started & Migration
How do I confirm my workflow cutover to Catalyst was successful?
Your Catalyst workflow cutover counts as successful when you complete targeted validation steps tied to specific operational and business goals. Compare production traffic patterns between your prior production engine and Catalyst, validate all workflow steps run without unexpected failures, confirm alerting and monitoring function as configured, and check that workflows deliver intended business outcomes. Keep in mind durable execution containment is not prevention, so actively monitor for unintended workflow leaks.
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.
