Versions and publishing
A workflow has one draft and any number of published versions. The draft is what the builder edits and what Run draft runs. Publish freezes the draft as the next numbered version: v1, v2 and on. The newest version is the live one. Schedules, app events and API runs use it, and it keeps running unchanged while you edit the draft, until you publish again. Nobody runs the live version by hand: Run draft always runs the draft.
The builder header and the project page show where a workflow stands:
| Status | What it means |
|---|---|
| Draft | Never published |
| Live · v4 | Version 4 is live and its triggers listen |
| Paused · v4 | Version 4 is live, but its schedule and app event triggers are off |
Publish a version
Section titled “Publish a version”- Test the draft with Run draft. See The builder.
- Press Publish in the builder header.
Publish saves the draft, checks it, then makes it the next version. “Version 4 is live” confirms it. Then:
- Schedule triggers aim at their next date and time, in your browser’s time zone, which the version records.
- App event triggers subscribe through their connections. Subscriptions no live trigger uses any more are removed.
- Runs already under way finish on the version they started with.
Any member can publish. An organization key can publish through the API too.
What Publish refuses
Section titled “What Publish refuses”When a check fails, no version is made. The draft itself is already saved. When the problem is in one node, the message names it, and the node is selected with its panel open.
| Message | What to do |
|---|---|
| Add a trigger to start the workflow | Add a Trigger |
| … leads into a trigger | Remove the edge that ends at a trigger |
| … has no incoming edge, so it would run on every run | Connect the node, or delete it |
| The workflow loops back on itself | Remove the edge that leads back to an earlier node |
| set a start date | Give the Schedule trigger a start date |
| choose a connection and an event | Finish the App event trigger |
| choose an action | Pick the Action node’s action |
| Choose a connection for … | Pick the Action node’s connection |
| … isn’t connected: an admin can connect it in Apps | Ask an admin to connect the app |
| add an address to send to, add the webhook’s URL | Finish the Notification node |
| choose a database, write the SQL to run | Finish the Database node |
| choose an agent, its agent no longer exists | Pick an agent in the Agent node |
| A Liquid message with a line and column | Fix the template it names |
Two more refusals come from outside the diagram:
- Your plan’s active app subscriptions. Publishing past the cap is refused before anything is subscribed. See Triggers.
- An app refuses a subscription. The message is the app’s, such as a missing permission, and no version is made.
A node missing a required setting is also marked on the canvas before you publish.
Publishing while paused
Section titled “Publishing while paused”A paused workflow can still publish. “Version 4 is published; resume to turn its triggers on” confirms it, and the triggers stay off until you press Resume, in the builder header or under More on a phone.
See past versions
Section titled “See past versions”Versions are listed newest first, the live one marked Live:
- In the builder, under Runs, then Versions.
- On the run history page, from More then Full history. It also shows who published each version and its time zone.
Every run records the version it ran, or Draft.
Going back
Section titled “Going back”There is no button that restores an older version. A run keeps the diagram it ran: open an old run in the builder, and when the draft has changed since, Show its diagram shows that diagram read-only. To go back to it, change the draft to match and publish again.