Troubleshoot Scheduled Integrations

Learn about troubleshooting scheduled integrations in Oracle Integration.

Topics:

Scheduled integrations may be queued and not execute on time as scheduled for the following reasons.

There is a running instance of the same scheduled integration. No new instance of the same integration is executed until the running instance completes.
The throttling limit for scheduled integrations has been reached. No new scheduled integrations are executed until the number of scheduled integrations being executed falls below the throttling limit.

Note:
The throttling limit is automatically adjusted based on available system resources.

An instance of a scheduled integration can be terminated by a user or Oracle Integration for the following reasons.

A user cancels a scheduled flow.
A user call reactivates a scheduled integration, which causes the currently-queued scheduled instance to be terminated.
A scheduled flow execution exceeds six hours, which causes Oracle Integration to terminate the scheduled instance.

There are several reasons for Oracle Integration to terminate a scheduled instances.

To prevent an integration execution from occupying the limited resources allocated for scheduled integrations for a long time, which can block other scheduled integrations.
To prevent a stuck integration (for unexpected reasons) from blocking subsequent runs of the same integration.
A scheduled integration is considered stuck under the following circumstances:
- For a scheduled integration without parallel processing (that is, no parallel for-each, reading of multiple files, or stage file action read file in segments operation), the total execution time exceeds six hours.
- For a scheduled integration with parallel processing (that is, parallel for-each, reading of multiple files, or stage file action read file in segments operation), the execution time of a batch or pre/post execution of a parallel execution exceeds six hours.