Validating that your flow is ready to run

When you create, edit, or import event-driven or API flows, App Connect automatically validates each application or Toolbox node in the flow.

If validation errors are detected, a warning icon Warning icon for flow validation is displayed on any nodes that require your attention. (If you're creating a flow, you might see the warning icon for a node only after you move to another node.) Validation errors are typically reported for unconnected or disconnected accounts, missing data mappings in required fields, and invalid syntax in JSONata expressions that you type into fields. To be able to start the flow, you must resolve all validation errors.

You should also check each node with a connected account to validate that the account has the connection details that you want to use and, if needed, update the connection details or switch to a different account. For more information about checking and changing accounts, see Managing accounts in App Connect.

To resolve a validation error, complete the following steps:

  1. Hover over the warning icon Warning icon for flow validationto see information about the validation error.
  2. If the validation error is Not connected, it's typically because you haven't yet connected App Connect to the related app, or because you need to re-authorize your account. To connect to your account for the app, click the node for that app, click Connect, and then follow the prompts to specify the account credentials. To re-authorize your account, you must update the connection details for that account, as described in Managing accounts in App Connect.
    Validation error example

    You'll also see a Not connected validation error if an app in an imported flow is connected to multiple accounts in App Connect, or if the account name used in the imported flow definition (YAML) file is different from the account name in App Connect. To resolve this error, click the Not connected drop-down list and then select the required account.

    Resolving a Not connected error for multiple accounts
  3. For other types of validation errors, examine and update the field selections for the node as required. For example, you might need to complete a required field (such as the To field for a Gmail > Create message action), or use a drop-down list to select an alternative preconfigured value that is specific to your account (such as a channel where you want to post a message for a Slack > Create message action), or correct invalid JSONata in a field. Sample errors for these three instances are shown below.
    Validation error for a required field
    Validation error example for a drop-down list value
    Validation error for invalid JSONata

    For example, if you select an action node with a validation error, you might see a configuration option with a message like the following: 

    
No object with ID "CKW5TC0J2" exists in the target system.
The current value is not available.

    This indicates that the option, stored with the internal ID shown is not known in your application instance. To fix the error, simply select an alternative option that is available; for example:

    Slack / Create message action configuration field to select a channel or user to post messages

    (Click image to view full size.)

Tip:
  • If multiple validation errors are detected, you'll see the total number and will need to resolve each error in turn.
    Multiple validation errors

    The number decrements as you resolve each error.

  • If you're working with an API flow, and you've accessed the Operations tab for a model, you might see a warning icon Warning icon for flow validationon the Edit flow button for some operations. This type of validation error indicates that the flow is incomplete. To resolve the issue, edit the flow and resolve validation errors there.
    Validation error for an operation in an API flow