Workflows & drafts
A workflow belongs to one server and does one job — greet newcomers, run tickets, hand out roles. This page explains the lifecycle every workflow moves through, because it shapes how you edit with confidence.
Draft and live are separate
Open any workflow and you're looking at its draft — a private working copy. The live version, if one exists, keeps running untouched while you edit. This split is what makes the editor safe:
- You can rip half the graph apart mid-afternoon; your server never notices.
- You can keep a rough idea parked in a draft for weeks.
- Publishing is a deliberate act, never a side effect of editing.
The dashboard shows you at a glance which workflows are live, which have unpublished draft changes, and which have never been published.
The editing loop
Day to day, building looks like this:
- Edit the draft on the canvas.
- Save — your changes persist, still private to the draft.
- Validate — the editor checks the whole workflow and lists anything incomplete or broken, with a click-through to the exact block.
- Publish — the draft becomes the new live version.
You don't have to run validation manually — Publish runs every check anyway — but the Validate button is handy while you're mid-build and want to know what's left to finish.
Versions and rolling back
Every publish creates a numbered version, and old versions are kept. If a newly published workflow misbehaves, you can put the previous version back while you fix the draft — no frantic rebuilding from memory.
This history is also your audit trail: who published, when, and what changed between versions.
Working alongside others
Drafts are shared per workflow, not per person. If a teammate saves while you have older changes open, the editor refuses to silently overwrite either of you — the second save is stopped and told the draft moved on. When that happens, reload and reapply your change. For bigger builds, agree on who owns a workflow's draft at a time.
Archiving
When a workflow has run its course, archive it rather than deleting. Archiving takes it out of service while keeping its history and versions browsable — and it can be restored later. Deleting is guarded separately; see Monitoring for what Juno checks before letting a workflow disappear for good.