You built a Workflow, opened Mando on another computer or browser, and the flow is gone. Nothing was lost from your account: Workflow drafts are saved only in the browser you build them in.
Why drafts do not travel
While a Workflow is a draft, it lives in your browser's local storage, not on Mando's servers. Local storage is tied to one browser on one device, so a draft you made in Chrome on your laptop is not in Safari, on another computer, in an incognito window, or after you clear site data.
[SCREENSHOT] Capture: the Automations list on a browser without the draft. Highlight: a live Workflow card showing 0 nodes. Suggested alt text: "A Workflow draft missing on another browser in Mando". Replace this block with the image.
What publishing does and does not do
Turning a flow Live saves a copy on the server, so the live flow shows up in the Automations list on other browsers. It does not copy the editable draft across, though: on a browser without the draft, a live flow's card shows 0 steps and cannot be opened for editing there.
How to avoid losing a flow
Do your editing on one browser, and use Save draft before you leave: an Unsaved status means the change is not even stored locally yet. To edit on another device for now, rebuild the flow there from the browser that holds the draft.
Frequently asked questions
Did I lose my work?
Only if you cleared site data on that browser. Otherwise the draft is still on the browser you built it in.
Why does the live flow show 0 nodes elsewhere?
The step count comes from the local draft, which is not on that browser.
Can I move a draft between devices?
Not yet. Keep editing on the browser that has it.