Validating your flow

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 mandatory 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.

Also check each node with a connected account to validate that the account has the connection details that you want to use. If necessary, update the connection details or switch to a different account. For more information, see Managing accounts.

To resolve a validation error, complete the following steps.

  1. Hover over the warning icon Warning icon for flow validation to see information about the validation error.
  2. A validation error of Not connected typically means that App Connect isn't yet connected to the related application, or you need to reauthorize 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 reauthorize your account, you must update the connection details for that account, as described in Managing accounts.
    Validation error example
    A Not connected error also appears when an application in an imported flow is connected to multiple accounts in App Connect. Or when the account name in the imported flow definition (YAML) file is different from the account name in App Connect. To resolve this error, click Not connected, then select the appropriate 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 where appropriate. For example, you might need to complete a mandatory field (such as the To field for a Gmail > Create message action). Or you might need 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 you might need to correct invalid JSONata in a field.
    Validation error for a required field
    Validation error example for a drop-down list value
    Validation error for invalid JSONata
    If you select an action node with a validation error, you might see a configuration option with the following example message. 
    
No object with ID "CKW5TC0J2" exists in the target system.
The current value is not available.
    This message indicates that the option, which is stored with the internal ID that is shown, is not known in your application instance. To fix the error, select an alternative available option.
    A Slack "Create message" action configuration field to select a channel or user to post messages
Tip:
  • If multiple validation errors are detected, you see the total number and 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 accessed the Operations tab for a model, you might see a warning icon Warning icon for flow validation on the Edit flow option 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