Flow Drafts and Publishing

What this does

Drafts let you make changes without affecting the live flow. Publishing applies those changes to the live version.

Draft status (what you’ll see)

• Draft: Unsaved = you’ve made changes but haven’t saved yet
• Draft saved: Not Published = your changes are saved but not live
• Published = you are viewing the live flow

Flow run status

• Active: new trigger events can start contacts in this flow.
• Inactive: the flow stays available for edits, but new trigger events do not start it.
• Paused processing: if an already-enrolled contact reaches a queued step while the flow is inactive, Hiveality pauses that step and checks again later instead of sending messages from an inactive flow.
• Removed flows: queued steps stop when the flow has been removed.
• Draft changes still require Save Draft and Publish to update the live version.

Connected assistants and API key workflows can activate or pause a reviewed flow without changing the draft content. Activation makes the published flow ready for new enrollments; it does not publish unsaved dashboard edits.

Save a draft

Publish a draft

After publishing, the builder reloads the live version while keeping the status indicator steady. If you click Publish again while a publish is already finishing, Hiveality ignores the duplicate request.

When you publish, Hiveality uses the current editor snapshot so the latest saved step and trigger changes are included even if the background save is still catching up. Very large drafts may need to be simplified before publishing.

Board wait review before publish

If a flow uses board-stage waits, publishing may show a review step for active contacts already waiting in that flow.

• Publish unchanged keeps current waiting contacts exactly as they are.
• Publish & resync waits updates their stored board-stage wait settings to match the newly published flow without sending messages or moving cards.
• If contacts have already moved past the stage the flow was waiting for, resync is not needed. The review may show Publish anyway and ask you to handle the board-side catch-up separately.
• The review lists affected contacts, cards, and stages so you can decide whether the current wait should be preserved or refreshed.

Use the warning count in the flow toolbar to reopen this review while you are checking a flow that has board-stage waits.

Draft-aware automation edits

Connected assistants and API key workflows can make focused step edits and trigger updates, but they respect the same draft boundary as the dashboard.

• If a dashboard draft is pending, publish or discard it before asking an external workflow to edit steps or set a trigger.
• Trigger updates validate the referenced tag, list, form, quiz, board, or booking service before saving.
• Step edits keep active contacts on valid steps when possible, but you should still test with one contact before activating a changed flow.
• Pause a flow when you want to stop new contacts from entering while you review the next draft.

Discard a draft

Tips

• Publish only after you’ve tested with one contact: see Flow Testing.
• If you only need a milestone cutoff, consider Flow Goals.
• Drafts are not auto‑saved. Use Save Draft to keep your progress.