Saving and publishing
Draft versus published, what blocks each, discarding a draft, enabling and cooldown.
| Action | What it does | Blocked by |
|---|---|---|
| Save draft | stores your working copy; the hub keeps running the published graph | nothing except "no changes" and the three size limits |
| Publish | copies the draft over the published graph and clears the draft; the hub reconciles and starts running it | any error-level validation issue and the size limits |
| Discard draft | throws the working copy away and reloads the published version | — |
The banner above the canvas says where you are: Not published yet — this flow only runs once you publish it, or Editing a draft — the published version keeps running until you publish.
Errors versus warnings: errors (duplicate ids, invalid options, dangling connections, size) block Publish; warnings (orphans, loops, redundant conditions) are saved and run as they are. The full table is on Validation messages.
Enabled
The toggle in the header (and on each row of the Flows list) switches a flow off without deleting it. A disabled flow keeps its published graph and can be enabled again later. Disabling does not discard drafts.
Cooldown
Cooldown… in the header menu sets a number of seconds (up to a day) during which new starts of this flow are refused after one starts — for every start, trigger or link. Use it for noisy triggers such as motion or sensor readings.
Unsaved edits
Switching tabs, opening another flow, or closing the editor does not lose unsaved edits: each open flow keeps its own working copy until you save or discard. See Tabs and working copies.