Saving versions
Each time you save a workflow, OrchaSync stores a version — a complete snapshot of the workflow at that moment. Your workflow is really a stack of versions, newest on top.
Why versions matter
- History — you can see how a workflow changed over time.
- Safety — if a change causes problems, you have the previous version to fall back on.
- Confidence — you can edit freely, knowing a saved version is preserved.
What's saved
A version captures the workflow's graph — its nodes, their settings, and the connections between them. Temporary, run-only state (like the live colors shown during a test run) is not saved; only your actual design is.
tip
Save a version whenever you reach a working state, not just when you're completely done. Frequent versions give you more points to return to.