Testing, Versioning & Release
What versioning rules apply to changes to agent workflow state schemas?
All updates to agent workflow state schemas on Diagrid Catalyst, its Dapr-based AI-native agentic durable execution platform, require backward-compatible changes. Add new state fields without removing or renaming existing ones, and ignore unrecognized incoming fields during normal workflow processing to preserve compatibility with active running agent executions. This standard practice does not prevent workflow breaks caused by partial state updates that rely on removed legacy data.
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.
