Testing, Versioning & Release
What versioning strategies work for backward-compatible workflow state changes?
Use additive-only workflow state changes to enable backward-compatible updates for agentic durable execution workflows with Catalyst. Avoid removing existing fields or altering their established data formats, route all new workflow runs to the updated schema while letting active legacy runs continue using their original state structure unmodified without disruption. Note that legacy running workflows will not access newly added state fields until they complete their current execution cycle.
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.
