✏️ Editing, Versioning & Publishing Flows

Article content

Flows in Flows Building can be updated at any time to reflect new requirements, fix issues, or improve behaviour.

This article explains how editing works, how changes are applied, and what happens when you publish a flow.

Editing an Existing Flow

To edit a flow:

Open Flows Building
Select the flow you want to update
Make the required changes to triggers, conditions, or actions
Save your changes

Saved changes are not live until the flow is published.

Understanding Draft vs Published Flows

Flows exist in two states:

Draft

Contains your latest saved changes
Can be edited freely
Does not affect live behaviour

Published

Is the active version of the flow
Responds to real events
Runs automatically when triggers occur

Editing a flow creates a draft version until you publish again.

Publishing a Flow

Publishing applies your draft changes and makes them live.

When you publish:

The current draft replaces the previously published version
The flow immediately begins running with the new logic
Any events that meet trigger conditions will be processed

Publishing is required for changes to take effect.

Versioning and Change Management

Flows Building maintains logical separation between drafts and live flows, which helps prevent accidental changes.

Best practices for managing changes

Make one change at a time
Save frequently while editing
Publish only after testing
Avoid major changes during peak usage periods

Keeping changes small makes issues easier to identify and reverse.

Testing After Publishing

After publishing a flow:

Run test events where possible
Confirm expected actions occur
Monitor behaviour shortly after changes

If issues appear, you can edit the flow again and republish a corrected version.

Unpublishing a Flow

You can unpublish a flow if needed.

When a flow is unpublished:

It stops responding to triggers
No actions are executed
The configuration is retained for later use

Unpublishing is useful during maintenance or investigation.

Common Editing Mistakes

Some common issues include:

Forgetting to publish after making changes
Publishing incomplete drafts
Making multiple changes at once
Not testing updated logic

Taking time to review changes before publishing reduces risk.

When to Update a Flow

You may need to edit and republish a flow if:

Business requirements change
Logic needs refinement
An issue is identified
External systems change behaviour

Regular reviews help keep flows reliable and relevant.

Setting up your first flow
Understanding triggers, conditions & actions
Common mistakes when building flows
Troubleshooting Flows Building issues

Appearance