Testing, Versioning & Release
How do versioning strategies work for durable agent workflows?
Standardized versioning for Catalyst’s agentic durable execution workflows uses unique identifiers tied to workflow definition updates to help avoid abrupt execution interruptions. In-progress workflow runs are routed to compatible existing definition versions, while new workflow launches use updated definitions to maintain operational continuity during iterative updates. Careful state transition testing is required to avoid invalid workflow runs when version mismatches occur between active and updated definitions.
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
What happens if I update a workflow definition while runs are active?
Covers safe practices for modifying workflow definitions while in-progress runs continue executing without unexpected interruptions.
