Getting Started & Migration
What factors help decide which agent workflows to migrate to Catalyst first?
Prioritize workflows with high business impact that currently suffer from unreliable execution or complex manual recovery. These benefit most from durable state and automated retries. A high-value workflow with moderate complexity allows you to demonstrate value with manageable risk. However, avoid workflows where external calls cannot be made idempotent without significant rework initially.
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.