Skip to main content
Editing a Flow alone does not affect production. Changes are applied to production after you publish.

Checking the publishing status

Check the Flow’s publishing status in the toolbar at the top of the canvas.
  • [Publish] The Flow has not been published yet.
  • [Update Ver.N] The Draft has been edited since the Flow was published. The button shows the version number that will be published next.
  • [Published] The current Draft matches the published version.

Publishing

  1. Click the [Publish] or [Update Ver.N] button in the toolbar.
  2. Review Changes to publish in the publish panel.
  3. Add a release note if needed. Release notes are optional and can contain up to 140 characters.
  4. Click the [Publish] or [Update] button in the publish panel.
Publishing saves the current Draft as a new version. Production then runs that version, while runs already in progress finish on the previous version.

Release notes

Release notes are optional. We recommend keeping them concise so changes are easy to understand later. The note appears in version history and audit logs. To publish a Flow in the active workspace from the CLI, use nora flows publish.

Conditions for publishing

The [Publish] or [Update Ver.N] button is only enabled when all three of these hold:
  • You have the Owner or Manager role Members can edit the Draft but can’t publish.
  • The Draft has at least one Agent block empty Flows can’t be published.
  • There are unpublished changes since the last publish You cannot publish again if the current Draft matches the published version.
When a condition fails, the button is disabled and the reason is shown below it.

Changes diff

The top of the panel compares Draft vs the currently published version block by block.
  • Added new blocks.
  • Modified blocks with changed settings.
  • Removed deleted blocks.
Click a change to move to the corresponding block on the canvas and open its inspector. Use this to review changes before publishing.

Version history

You cannot edit the contents of a published version. When you modify and publish the Flow again, the changes are saved as a new version, while existing versions remain in version history. Click the View version history link at the bottom of the publish panel to see every published version. Each version shows its release note, publish time, and publisher. When you roll back to an earlier version, the selected version is applied to production again. Versions and publishing records from before and after the rollback are not deleted. See Rollback for details.

What to do next

Version publish

How publishing works and how to read the change history.

Rollback

Something broke? Point production back to a previous version.