Potential Errors when Saving a Flow

Potential Errors when Saving a Flow

There are several requirements that if not met will prompt errors when saving a Flow. A dialogue box like the one below will display.


You will also see caution icons above elements with errors to help you identify where to find and fix the errors. Errors with red caution icons must be fixed before the Flow can be saved. Yellow caution icons indicate an error on that element, but they will not prevent you from saving the Flow.


Errors that will prevent you from saving your Flow

The following errors will have red caution icons and must be corrected before you can save a Flow:

  • No form selected: To save a Flow, you must have a form selected for every Task. This is why we recommend documenting your process and creating every form needed before starting to build a Flow. If your form is not ready, you may select another form on the table to save the Flow and prevent temporary loss of work; however, you will need to remember to come back to the Flow builder to select the right form to avoid creating confusion for your end users.

    • Remember, a user’s role must have permission to access each form selected in the Flow. If the user’s role does not have the correct permission, the user will encounter an error while going through the Flow. You will not be notified of this potential problem when building and saving the Flow. We recommend testing your Flow using the intended role before implementing the Flow.

    • Similar to the form permissions, users must have access to the View selected for each Task. If the role does not have the correct permission for that View, the user will encounter an error when using the Flow.

  • Edit Child: An Edit task cannot immediately follow an Add task on a parent table. In the example below, the first step was to create a parent Purchase Order (PO), and the second was to edit a child line item on that PO. But in this example, TrackVia cannot know which record you wish to edit from the child Line Items table. To resolve this error, you must first use a View task to find the child record if it already exists (see the Tasks article), or you may use an Add task if you wish to create a new child line item for the parent PO created in the first step. This error must be resolved before you can save the Flow.


Errors that still allow a Save

The following errors will have yellow caution icons and will appear in a dialogue box but will not prevent you from saving the Flow:

  • A disconnected element: If you are still working on an element or aren’t sure where it will go, you can leave it disconnected on the canvas. Note that even a disconnected element that is missing a form will prevent you from saving the Flow.




Feedback and Knowledge Base