Publish, pause, or archive an eflow

Status is a dropdown in the eflow editor’s header, next to the title — visible from any tab, not just Overview. There are four values.

Pause is the one to reach for when you need to stop collecting now — while you fix a question, or because you have enough answers. It is reversible and it destroys nothing.

Moving to Draft after publishing does not un-send links you have already distributed to people; it stops them working. If you have printed a QR code, pause rather than redraft so the failure a customer sees is a closed conversation rather than a dead page.

From the list

The Eflows list changes status too, without opening anything. Each row ends in a ⋮ menu, and it offers only the moves that apply to that row right now: Publish on anything not already live, Pause on a published eflow, Archive on anything not already archived. Use the list when you are changing several eflows in one sitting, and Overview when you are already inside one.

Three things behave differently there.

• The list opens on Active, which hides archived eflows. Active is the first filter above the table and means every status except Archived: draft, published and paused together. Archiving something is what takes it out of this view. Nothing is deleted — click Archived to see them, and the count beside each filter tells you how many are in it before you click.
• Nothing in the product brings an eflow back out of Archived. The menu on an archived eflow drops Publish and Archive, and the status dropdown on that eflow’s own Overview page drops the same two, for the same reason — there is no UI path from Archived back to Draft, Published or Paused. Duplicate, on the row menu, is how you run it again: it makes a fresh draft copy of the questions and branches, and leaves the archived original and its responses where they are.
• Delete appears on archived eflows and nowhere else, and it only succeeds on one nobody has answered. There is no confirmation step and no undo, which is why archiving first is a required step rather than a habit.

If Publish or Delete is refused

Publishing past your plan’s active-eflow limit is refused. Every plan caps how many eflows can be live or paused at once — pausing one keeps its slot; only archiving frees it. If you are at the limit, archive an eflow you no longer need, or move up a plan for a higher ceiling. Resuming a paused eflow never hits this limit, since a paused eflow already holds its slot.

An eflow somebody has already answered cannot be deleted. Removing it would mean removing the conversations collected through it, and that is not something a row menu does — so archive is the end of the line for anything with responses. Archive is not a lesser delete here; it is the intended end state, and everything collected stays readable in Results.

When either refusal happens the list says so, above the table, naming the eflow and the reason. The row stays exactly as it was: both are refused before anything is written, so nothing is half-applied and nothing is lost.