Versions and deployment
A strategy definition is a name, a description and the history of the diagram’s versions. Each save of a changed diagram creates a new immutable version: v1, v2 and so on. The name and description change without a new version.
Deployment
Section titled “Deployment”A saved version is deployed to the execution engine. Definition statuses:
- Deploying — the version is still being deployed;
- Active — a version is deployed, the strategy can be run;
- Error — the engine rejected the version.
A definition cannot be run until one of its versions is deployed.
Active version
Section titled “Active version”New runs start on the active version — usually the latest deployed one. Runs that already exist stay on their version for good: editing the diagram never changes what is already trading.
The card shows it like this: “v3 is deploying — runs still start on v2” or “v3 was rejected by the engine — runs start on v2”.
Rollback and redeploy
Section titled “Rollback and redeploy”On the definition page, in Versions:
- Make active — move new runs back to any deployed version (rollback). Not available while the latest version is still deploying.
- Deploy again — resend a version the engine rejected.
- Compare — see the difference with the previous version.
Save conflicts
Section titled “Save conflicts”If the definition was saved in another tab while you were editing it, the editor will not overwrite that version: it offers to load the current one or open the history.