Getting Started & Migration
Which agent workflows should I migrate to Catalyst first to gain the most value?
Start with long-running, multi-step workflows that have costly failures today, such as document processing pipelines or approval chains. These benefit most from automatic state persistence and retry. Migrate those where partial completion leads to inconsistent state. Boundary: Avoid overly simple stateless calls; durable execution adds persistence overhead with little gain for trivial tasks.
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.