Find Integrations That Timed Out or Were Aborted

Being able to quickly find an integration that has timed out or been aborted can help you troubleshoot.

Why Integration Instances Have a Status of Aborted

Several activities can change an integration instance's status to Aborted, including the following:

• Someone canceled the integration.
• Someone stopped the scheduled of a scheduled integration.
• Someone edited a connection for a queued or in progress schedule integration.
• The integration timed out.

Time Limits for Integrations

Different integrations can run for different amounts of time. To see the time limits, see Service Limits in Provisioning and Administering Oracle Integration 3.

To Find All Aborted Integrations:

You can work on either the Instances or Integrations page.

1. Find all aborted integrations using one of the following options.
   • Filter the Instances page so it shows only aborted integrations.

     1. In the navigation pane, click Observability, then Instances.

     2. Click Filter , and from the Status dropdown, select Aborted.

     3. Update the other filters as needed, and click Apply.

        The page shows only aborted integrations.

   • Scan the Integrations page and look for any integrations with one or more aborted instances.

     1. In the navigation pane, click Observability, then Integrations.

     2. Review the Aborted column for any non-zero values.

        An integration with a non-zero value in the Aborted column has one or more aborted integration instances.

Next, determine why an integration was aborted. See Determine Why an Integration Instance Stopped Running.