Every flow has a draft (what you edit) and, once published, a live version (what triggers run).
| Draft | Published (live) | |
|---|---|---|
| Edited by | Everyone with the flow open, together, and the agent (Editing together) | Publish copies the draft |
| Run by | The editor (Test run, Run) | Schedule, Webhook, Form; and callers via Run flow |
| Shown as | Draft in the Studio list | v3 in the Studio list, Published v3 after publishing |
Publish
Press Publish. mooflair waits until the server has your latest edits, copies the draft as it is right now (the live document) to the flow's published field ({ version, graph, publishedAt }) and keeps a copy in the version history. Versions count publishes: v1, v2, v3.
Version history
Open Version history (clock icon). It holds:
- Publishes (the latest 50), numbered v1, v2…
- Snapshots of the draft: after a burst of edits, at most one every 10 minutes, when the graph changed (the latest 100).
- Named versions: Name current version (editors) keeps the draft as it is now under a name, for good.
Each entry shows who edited it (their avatars, in their color) and what changed since the entry before (added, changed, removed nodes). Filter All, Published or Named.
| Action | Does |
|---|---|
| Preview | Shows that version on the canvas, read-only, with changes marked. Hide returns to your draft. |
| Restore to draft | Editors: replaces the draft with that version for everyone. Your undo (⌘Z) brings it back. |
| Revert | Editors, on a named snapshot (a kept draft or suggestion): takes back only what that version changed since the one before it, keeping what changed after (like reverting a merge commit). A part changed again since is a conflict: undo it by hand. |
| Make live | Publishes only, for whoever may publish: that version goes live again, without touching your draft. |
The live version carries a Live badge.
Retry with the version a run used
The engine keeps the exact graph each run used. After you edit the draft, Retry from failed offers With the version it ran next to With the current version. See .
Changed since the run
A node edited after the run it shows gets an amber dot: "Changed since the run: its output may be out of date".
FAQ
I published but the schedule runs the old version.
Each start reads the published version at that moment; the next start uses the new one. A run already going keeps the version it started with.
Does deleting a flow delete its versions?
Yes, with its tests and agent conversations. Past runs stay on the engine.