Getting Started & Migration
What checks should I complete before cutting over to Catalyst?
Completing targeted pre-cutover checks helps mitigate unexpected operational issues when transitioning fully to the Catalyst platform. Next, validate that your staging environments fully match production configurations, confirm all key external dependencies work correctly with Catalyst, run comprehensive full end-to-end tests on your migrated workflows, and verify critical monitoring and alerting are properly configured for the new production deployment. Importantly, durable execution does not offer exact-once delivery without supplementary safeguards.
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.
