Testing, Versioning & Release
What versioning strategy works best for agent workflows?
Semantic versioning tied directly to workflow schema changes is a recommended strategy for production-grade agent durable workflows on Diagrid Catalyst. Tag every update to workflow definitions with a unique version identifier, map active workflow instances across clusters to their compatible schema versions to prevent incompatible execution conflicts and preserve consistent run behavior. Overusing dedicated version branches for minor incremental changes will increase unnecessary long-term operational overhead.
Was this article helpful?
Your feedback helps improve Diagrid's FAQ experience.
Keep reading
More Diagrid FAQ articles
- Testing, Versioning & Release
How do I test durable agent workflows that use LLM calls?
Covers testing durable agent LLM workflows: use replayable validation, mock LLM calls to avoid real APIs in local/staging tests, verify state transitions.
- Testing, Versioning & Release
What staging environment requirements apply to durable agent workflows?
Outlines key staging considerations for deploying and validating durable agent workflows before moving them to production environments.
- Testing, Versioning & Release
How do versioning strategies work for durable agent workflows?
Explains core versioning approaches for managing updates to durable agent workflow definitions and their associated execution runs.