Getting Started & Migration
What checks should I run before cutting over to Catalyst?
Run end-to-end validation tests for your migrated workflows before cutting over fully. Test edge cases like failed external calls, timed-out steps, and partial execution to ensure Catalyst handles recovery as expected. Compare output against your original engine to confirm consistent results across both platforms. Keep in mind that containment of workflow failures does not prevent all downstream impacts, so test cross-service dependencies thoroughly.
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.
