Find the Connections with the Most Errors

Knowing the connections that result in integration instances with errors can help you quickly prioritize integration failures and start the troubleshooting process.

Why Connections Experience Errors

The typical causes of connection errors are varied and depend upon the adapters you use, the way you use the connections, and your use cases. For example:

• The integration developer configured the connection incorrectly.

  In this case, the connection always fails.

• The connection cannot complete its task.

  Consider a connection that is based on the FTP Adapter. The connection fails if someone moves or deletes the folder that the integration reads from or changes the permissions on the folder.

To Find the Connections with the Most Errors:

1. In the navigation pane, click Observability, then Dashboards.
2. Along the top, select the Connections with errors metric.

   The Top connections with errors section appears, listing up to five of the connections with the most errors.

3. Below the Top connections with errors heading, point to the box for a connection.

   A tooltip displays the number of integration instances that use the connection and experienced an error.

4. Find the integration instances that used the connection and experienced errors.
   1. Click within one of the connections boxes.

      The Errors page appears and shows only the integration instances that used the connection and experienced an error.

   2. Hover over an errored integration instance, and select View details .

      The activity stream opens.

   3. In the activity stream, find the milestone with an error and open the activity stream from it using one of the following options.

      • If View payload appears on the milestone, click View payload .
        
        

      • If View payload doesn't appear on the milestone, expand the milestone by clicking the expand icon >, and then click View payload for the part of the integration flow that failed.
        
        

   4. Review the payload and take the appropriate action.

      For example, if a 404 error occurred, check the configuration of the connection.