Versioning and Environments

Draft vs. Published

Every save creates a version record. Drafts (published=false) represent work in progress. Publishing locks the version. It cannot be modified, only superseded by publishing a newer draft. All versions are retained for audit and rollback.

Environment Isolation

The recommended approach for strict separation is deploying separate hub instances for Development, Staging, and Production. Each instance has its own database, runners, and license. Workflows are promoted between environments by exporting the graph definition and importing it into the next environment.

Rollback Strategy

If a published version causes failures: 1. Disable all triggers for the workflow. 2. Wait for in-flight executions to complete. 3. Load a previous version's graph definition, save as a new draft, and publish. 4. Validate with a test run. 5. Re-enable triggers.