How to Save a Flow That Has Broken Connections

This guide shows you what to do when the Flow editor says some connections can't be saved.

Prerequisites

• Access to a Space where you can edit Flows

Why a Connection Breaks

A connection joins an output handle of one node to an input handle of another. A node's handles depend on its settings and on what it points at, so a handle can disappear after the connection was made. For example:

• A Flow - Execute node loses its Trigger input and its Success and Error outputs when the Flow it runs switches its trigger to data-only mode.
• A node that reads or writes a Schema loses a property's handle when that property is removed from the Schema.

The canvas can only draw a connection between two handles that exist, so a broken connection is not shown, and you can't click it to delete it. The editor still finds it when you save.

Remove Broken Connections

1. Click Save (or Save new version for a published version).
2. If any connections are broken, the Some connections can't be saved dialog opens instead of saving. It lists each broken connection by its nodes' names and handles, and names the handle each node no longer has.
3. Click Remove n connections to delete every listed connection, or click Show next to a connection to select its two nodes on the canvas and check them first.
4. Reconnect the nodes through handles they still have, if the Flow needs that link.
5. Click Save again.

Result: The Flow saves. Removing a connection changes what the Flow does when it runs, so check that the nodes it joined still run in the order you expect. Undo brings the removed connections back until you save.