Manage Errors
You can manage errors from the Errors pages in Oracle Integration. You can resubmit failed instances, discard failed instances, view message recovery status, and view basic and detailed error messages. You can also view and download the activity stream, which provides access to error messages and message payloads in failed instances.
View Error Messages and the Message Payload in the Activity Stream of Failed Instances
You can view error messages and the message payload in the activity stream of failed integration instances on the Errors page. You can also download the activity stream logs and the payload of the failed section of an integration instance.
- In the navigation pane, click Observability, then Errors.
- Perform the following tasks:
Filter the Display of Error Message Details
- Click
Filter to filter the display of errors by the following:
- Last updated or creation time
- Project (begin entering a name to display a list from which to select)
- Integration
Begin typing an integration name. Do not use copy and paste. The filter is refreshed to display fields for the defined secondary business identifiers.
You can now begin typing the values of the business identifiers to narrow down the search. This input follows the same rules (for example, for exact matches and phrase matches) as described in Search for Primary and Secondary Business Identifier Values.
- Error type (all, recoverable, or nonrecoverable)
- Instance ID
- Error message
For example:
- Enter part of an error message, such as
unknown
,unauthorized
, orendpoint
. - Enter an exact phrase match of an error message in double
quotes, such as
"Could not activate endpoint for endpointID"
- Enter part of an error message, such as
- Detailed error message
- Connection name
- Integration style (all, application, schedule, or event)
- Integration state (all, retained, or purged)
&filename
or"file tracking"
).
- Click Date Range in the Time Window section.
- Specify a custom time range with which to filter the search for errors with the From and To buttons. This functionality also exists on other monitoring pages such as the Instances page and Monitor Integrations page.
View Error Message and Payload Details on the Errors Page
Error message details can be displayed in two parts: a summarized error message for easy understanding and resolution and, if necessary, a more specific error message if more detailed troubleshooting is required. You can view error messages on the Errors page or by clicking on a business identifier to view the entire integration flow on the Instance Details page. You can also view the payload details in the activity stream of a failed instance.
- Hover over the row of the failed instance.
- Click View
. The Activity Stream panel opens. The activity stream shows details
about the movement of the message through the integration, including where any
failures occurred. The date and time according to your user preferences are
displayed.
- Click Download Logs at the top of the activity stream to download the activity stream logs for the entire instance.
- Scroll through, expand milestones, and click View
Payload
to view the payload for the part of the integration flow that failed.
An option is provided in the activity stream for quickly showing all error content only. This option can be especially useful for instances in which a logic action such as a for-each loop or while loop with many iterations has failed. This option enables you to jump quickly to the iteration that failed instead of scrolling through each iteration of the loop to access the errors. Show errors in either of two ways:
- Click View Errors
to view only the errors in the activity stream. This persists the selection of errors in
the activity stream across multiple instances until you deselect the
button. This button enables you to toggle between showing only errors
and showing all content in the activity stream.
or
- Click the error in the activity stream banner to jump to
that specific error.
- Click View Errors
to view only the errors in the activity stream. This persists the selection of errors in
the activity stream across multiple instances until you deselect the
button. This button enables you to toggle between showing only errors
and showing all content in the activity stream.
- Perform tasks within the failed part of the payload.
Element Description Download Payload Click to download this part of the payload to your desktop. Copy Payload Click to copy this part of the payload for pasting into a document. Toggle Line Numbers Click to show or hide line numbers in the payload. or
- Hover over the row of the failed instance.
- Click Expand
to view a summarized version of the error message for easy
understanding and a detailed version that describes how to resolve the error.
View the Flow of the Failed Instance and Payload Errors in the Activity Stream on the Instance Details Page
You can view the flow of the failed instance to identify any trigger, actions, or invokes in error on the Instance Details page. You can also drill into those elements to view specific error messages and payload errors.
- Click a specific business identifier of an integration instance in
the Primary Identifier column.
The integration flow of the failed instance and Activity Stream panel are displayed.
- Scroll through the flow to find the trigger, action, or invoke in error.
- Click the element, then click Actions
and select View Error.
The Activity Stream panel opens to the specific section at which the error occurred. For this example, the error occurred in an integration action (parent integration calling a child integration) of a parallel for-each action. All five of the iterations of the parallel for-each are displayed for viewing in the activity stream.
- Scroll through and view the errors.
- Click Activity Stream to close the activity stream. This link operates as a toggle for closing or opening the activity stream.
- Click the failed trigger, action, or invoke again, then click
Actions
and select Activity Stream.
This also opens the Activity Stream panel to the specific section at which the error occurred.
- Scroll through the payload and expand the sections in error to view specific details.
- Click View Payload
to view the payload of the section in error.
- Perform other tasks within this section.
Element Description Summary Click to view a summary of payload details. This action also highlights the section of the integration flow in error. Details Click to view more specific payload details. This action also highlights the section of the integration flow in error. Download Payload Click to download this part of the payload to your desktop. Copy Payload Click to copy this part of the payload for pasting into a document. Toggle Line Numbers Click to show or hide line numbers in the payload. - Click Activity Stream to close the activity stream.
Resubmit Failed Messages
You can manually resubmit failed messages. Oracle Integration does not automatically resubmit failed messages. After resubmitting an instance, you can track all resubmissions of that instance on the Instances page. You can also change the tracing level for a resubmitted message.
- From the beginning of the integration.
- From another location in the integration, depending upon the design. For example, if there is a wait activity in the integration prior to the recoverable fault, then resubmitting the fault starts the integration just after the wait activity.
-
Single failed message resubmissions
-
Bulk failed message resubmissions
There is a time window for recovering a failed integration instance that's recoverable. See Service Limits in Provisioning and Administering Oracle Integration 3.
Error instances that are resubmitted and successfully resolved are
removed from the error list. If an instance is resubmitted and is in progress, a
state of In Progress
is displayed in the list. During this state,
additional resubmissions of this error instance are not permitted.
Note:
Do not discard a message that you want to resubmit. A discarded message cannot be resubmitted.-
In the navigation pane, click Observability, then Errors.
-
Click Filter , then select the time period or retention period during which to search for integration errors.
-
Resubmit errors in either of two ways:
-
Hover over the row of the specific error to resubmit.
-
Click Resubmit .
The Resubmit instance panel opens.
- Select the tracing level to use for the resubmitted
instance. When resubmitting an errored integration instance, you can
change the level of tracing (production, audit, or debug) for just this
specific resubmitted instance. Increasing the tracing level (for
example, setting it to Debug) enables you to view
more specific information about errors in the activity stream and
downloaded logs. This setting applies only to this instance and does
not change the tracing level set when the integration was
activated.
- Production
- Audit
- Debug
The tracing options provide different levels of information logging. See Activate an Integration.
When the instance resubmission completes, the activity stream provides details. The tracing level shown at the top represents the level set during integration activation. To see details about the tracing level set for this specific resubmission, scroll down to this message:Recovery process initiated (Tracing level: Debug)
Or
-
Select the check boxes of errors to resubmit together. Only instances identified by the Resubmit icon that is visible when you hover over a row can be resubmitted.
-
Click Resubmit in the upper right corner.
Note:
This method of message resubmission does not allow you to select the tracing level to use for the resubmitted instance. Instead, the tracing level selected during integration activation is used.
-
- Click Confirm to resubmit the instance when
prompted.
A Resubmission summary panel opens with details about the instance being resubmitted for processing. Click Refresh to see if it still appears on the Errors page before trying another resubmission.
Instances aren't accepted for resubmission for the following reasons:- The instance is not recoverable.
- The instance has reached the maximum number of retries limit.
- The instance has not yet reached the deadline for recovery set internally for batch processing.
You can track all instance runs (both the initial run and all resubmissions) above the activity stream on the Instance Details page.
- In the navigation pane, click Observability, then Instances.
- Click the instance name.
- Note the number of instance runs above the Activity Stream panel.
The number 1 indicates that this is the first run of the integration.
<- 1 of 2 submissions ->
- Click -> to access tracking details for
the first resubmission of this instance (that is, the second run of this
instance).
The status for the first resubmitted instance is displayed.
- Click the <- to return to the tracking details for the first run of this instance.
Discard Errors
You can discard errors based on the integration in which they occurred. A discarded error message is removed from the Errors page and can be seen in an aborted state on the Instances page. You cannot perform any further operations on a discarded message, including recovery. After a certain time period, the error message is permanently deleted from the server.
View the Status of Message Recovery
You can search for and view the status of failed messages that have been submitted for recovery on the Errors page.
-
In the navigation pane, click Observability, then Errors.
-
Submit a failed message for recovery.
-
From the drop-down list at the top right, select Error Recovery Jobs.
-
The Error Recovery Jobs page is displayed for viewing the status of message recovery.
-
Received: Recovery is still in progress.
-
Succeeded: Recovery succeeded.
-
Errored: Recovery failed.
-
View Errors By Integration and Connection
You can view errors by integration and connection on the Errors page.
-
In the navigation pane, click Observability, then Errors.
- From the drop-down list at the top, select an option:
- To view errors by integration, select Errors by integration.
- To view errors by connection, select Errors by connection.
- If you selected Errors by integration or Errors by connection, click Filter to show errors alphabetically by name or by error count in descending order.
- Click the error count for an integration or connection to invoke the Errors page and view all errored-out instances for the given integration or connection.
- Hover over an integration:
-
Click Retry to resubmit errors.
- Click Abort to discard errors.
-