Several common issues can result in performance issues for an integration. For example, when the target application takes longer than expected to respond, the integration also runs slower than expected.

Consider a scenario in which 100 integration instances typically run by a specific time of day, but only 80 integration instances have run by that time today. You need to quickly determine what happened with your missing integration instances.

1. Determine how many integration instances have run so far.
   1. In the navigation pane, click Observability, then Instances.
   2. Click Filter , and update the filtering requirements for the page.

      For instance, update the time window to the last 1 hour, 6 hours, or 1 day.

   3. At the top of the page, review the count of the number of integration instances that ran.
2. If fewer integration instances have run than expected, troubleshoot the missing instances.

   For instance:

   • Check whether the integrations are active.

   • Check whether an external application that triggers an integration is down.

   • Check whether someone changed the schedule for a schedule integration.

   • If needed, consult the audit trail to determine who last updated an integration.

     See Check the Audit History for an Integration or Other Component.

If Oracle Identity Cloud Service is configured with multi-factor authentication (for example, user name / password + multi-factor authentication) and you use basic authentication to invoke Oracle Integration services, you receive a 401-Unauthorized error. None of the adapters or the connectivity agent in Oracle Integration support multi-factor authentication.

See Managing Multi-Factor Authentication.

When the message payload in an integration exceeds the size limit, the message is rejected and an error message is displayed. The error message describes remedial actions to perform.

CASDK-0059: Unable to process the response received from the client application. 
The response received by the OIC integration flow is rejected.
The response received has been rejected since the content received of length  
bytes exceeds the maximum allowed threshold of 1073741824 bytes (1GB).

For additional details about 50 MB payload support, limits, and best practices, see Service Limits in Provisioning and Administering Oracle Integration 3.

Oracle Integration does not support certain non-printable control characters in the following range.

['\u0000', '\u0001', '\u0002', '\u0003', '\u0004', '\u0005', '\u0006',
'\u0007', '\u0008', '\u000b', '\u000c', '\u000e', '\u000f', '\u0010', '
\u0011', '\u0012', '\u0013', '\u0014', '\u0015', '\u0016', '\u0017', '\
u0018', '\u0019']

{
  "type" : "10.4.1",
  "title" : "exception occurred while translating the request from native to
xml.",
  "detail" : "oracle.cloud.connector.api.CloudInvocationException:
ORABPEL-15235\n\nTranslation Failure.\nFailed to translate JSON to XML.
org.codehaus.jackson.JsonParseException: Illegal unquoted character
((CTRL-CHAR, code 1)): has to be escaped using backslash to be included in
string value\n at [Source: java.io.BufferedReader@.#; line: 2, column:
22]\nThe incoming data does not conform to the NXSD schema. Please correct
the problem.\n",
  "o:errorCode" : "TRANSLATION-ERROR-00",
  "o:errorDetails" : [ {
    "type" : "NA",
    "instance" : "NA",
    "title" : "NA",
    "o:errorPath" : "NA",
    "o:errorCode" : "NA"
  } ]
}

If you receive this error and are using the REST Adapter, you can use the Skip Control Characters property in the mapper. See Set REST Adapter Connectivity Properties in the Mapper. Otherwise, contact Oracle Support for information on how to preprocess incoming JSON payloads and filter unprintable control characters.

If the notification action in an integration validates successfully, but the following error occurs during integration runtime, the value specified in the Parameter Value field of the notification action may be incorrect.

:
summary=<summary>The <from> value is invalid.
Xpath expression associated with <from> in copy assign activity is invalid.
There is an user error that results in missing element value(s) in the xpath query.
Please review the payload and modeling to ensure that all elements defined in the <from> xpath query have valid non-null values .
</summary>
:
,query=<query>fn:current-dateTime()</query>

The error can be confirmed by viewing errors for the integration instance on the Instances page or the response of a REST testing tool such as Postman.

string(fn:current-dateTime())

If a synchronous integration fails to complete within 300 seconds, the following error appears in the activity stream that is viewable from the Instances page or Errors page.

CompositeException in: io.reactivex.internal.operators.single.SingleOnErrorReturn$OnErrorReturn.onError2 exceptions occurred

No details are returned when the call is processed (for example, no 502 status error is returned).

Optimize your integration and/or the endpoint you invoke to complete instance processing in under 300 seconds.

See Service Limits in Provisioning and Administering Oracle Integration 3.

You can enable tracing with the payload, view the activity stream logs on the Instances page, and download the activity stream logs with the REST APIs.

You may observe that Oracle Integration sometimes takes three to four seconds to go from Message Received:Instance created and enqueued for processing to message dequeued and processed by Trigger trigger_name. This increases the end-to-end processing time of a particular instance.

This is the expected behavior with asynchronous requests. Asynchronous requests are processed using a queue. The first two entries in the flow logs show the enqueue and dequeue times. Therefore, a few seconds lag is expected.

OAuth enables Oracle Integration to access a user's resources on their behalf. REST and other REST-based adapters (such as Google Calendar Adapter, Microsoft Office 365 Outlook Adapter, and others) often access APIs that are protected using OAuth. If these calls result in a 403 error (forbidden), it usually indicates a lack of permissions to access the API.

The certificate that you receive from a Certificate Authority (CA) such as Verisign, Entrust, or others can fail during import into Oracle Integration with the following error in the log file:

java.security.cert.CertificateException: Unable to initialize,
java.io.IOException: extra data given to DerValue constructor