Repair an invalid flow

You can't save a flow that has an invalid structure. Three typical causes of invalid flows are:

  • Required inputs not present

  • Invalid isolated method

  • Invalid fields

  • Invalid error handling

Required inputs not present

Required inputs are marked with a red asterisk next to the field name. Scan all your cards to make sure that you've assigned a value to all required inputs.

If your flow has branches (for example, if it uses an If/Else) you should look inside the branches as well. Any invalid card typically shows a red title.

Invalid isolated method

Sometimes an Invalid isolated method alert appears on several, or even all, of the cards in your flow.

This error usually results when a field is mistakenly mapped from the right to the left. You may have to search through all of your cards to find the error. To help locate these kinds of errors, you can turn on the X-Ray view. Click the X-Ray button found at the right side of the toolbar above your flow.

For example, consider the scenario of a flow with a Math Add card that sums the outputs of two previous cards. If you move the Math Add card to the left of one of those two source cards, then Invalid isolated method alerts appear. Moving the Math Add card back to a point after the source cards removes the alerts.

Invalid fields

The Some fields are invalid alert happens if you map a field from inside a branch to a card outside of the branch.

For example, mapping the False branch of an If/Else to a later card. This is invalid because that field doesn't exist if a different branch is run.

The alert goes away if you move the destination card inside the same branch as the source field. Or, if you want to use fields from inside a branch to the outside, use branch Outputs to assign a value from each branch that does map to later steps.

Invalid error handling

If your flow contains error handling that isn't valid, then the flow can't be saved or executed.

For example, if you select the Run another flow option in the error handling for a card, but you don't enter a helper flow where the Workflows can return the error details. This sequence means that the error handling for the card is invalid, and so you can't save the flow.