Determine Why an Integration Instance Stopped Running
When a scheduled or asynchronous integration instance stops running, the reason for the termination appears in the activity stream.
- Someone Stopped an Asynchronous Integration Instance
- Someone Deactivated an Asynchronous Integration While Instances Were Running
- Someone Stopped a Running Schedule of an Integration
- Oracle Integration Terminated an Asynchronous or Schedule Instance That Exceeded the Processing Deadline
- Oracle Integration Terminated a Stuck Scheduled Instance
Someone Stopped an Asynchronous Integration Instance
- In the navigation pane, click Observability, then Instances.
- Hover over the row of the active integration instance to terminate,
and select Abort
.
- Click Confirm when prompted.
- Click View Details
.
The Activity Stream panel opens. A red icon and the reason for the termination are displayed.Instance aborted by username
Someone Deactivated an Asynchronous Integration While Instances Were Running
- In the navigation pane, click Design, then Integrations.
- Hover over the row of the integration instance to deactivate, and
select
.
- In the navigation pane, click Observability, then Instances.
- Click View Details
.
The Activity Stream panel opens. A red icon and the reason for the termination are displayed.Instance aborted due to deactivation of integration by username
Someone Stopped a Running Schedule of an Integration
The scheduled run is either currently running successfully or has exceeded six hours in duration (now considered an out-of-bounds run).
- In the navigation pane, click Observability, then Instances.
- Hover over the row of the active, schedule integration instance to
terminate, and select Abort
.
- Click Confirm when prompted.
- Click View Details
.
The Activity Stream panel opens. A red icon and the reason for the termination are displayed.Instance aborted as schedule was stopped by username
Oracle Integration Terminated an Asynchronous or Schedule Instance That Exceeded the Processing Deadline
- In the navigation pane, click Observability, then Instances.
- In the Duration column, find the integration that has exceeded the processing deadline (for example, an integration's duration reached eight hours and two minutes).
- Click View Details
.
The Activity Stream panel opens and displays the following details for the instance terminated internally by Oracle Integration.Instance aborted as it has reached maximum duration allow for a flow
Oracle Integration Terminated a Stuck Scheduled Instance
This rare scenario is for scheduler recovery jobs and only applies when a schedule instance is not terminated internally by Oracle Integration.
- In the navigation pane, click Observability, then Instances.
- In the Duration column, find the integration that has exceeded the processing deadline.
- Click View Details
.
The Activity Stream panel opens and displays the following details for schedule instances.Instance aborted as it has reached maximum duration allow for a scheduled flow