Component: Integrations

Resource Service Limit
Active integrations
Integration invocation depth

  • 16 invocations

    For example, a parent integration (schedule integration) invokes a child integration (application integration), which in turn recursively invokes the parent integration.

    Integration entry points along the request execution path are counted towards the limit. When 16 is exceeded, it results in an error.
String size limit

If the size of a string variable exceeds 10,000 characters, a warning message is shown in the activity stream. Oracle Integration does not currently impose a limit on the size of string variables. However, this may be subject to change in the future, which could result in a flow execution failing when the limit is exceeded.

Parallel action concurrency Parallel action branches independent of the integration type (synchronous, asynchronous, and so on) count towards the concurrency limits on synchronous requests.

For example. a parallel action with three branches needs two extra concurrency slots for the duration of the parallel action; one branch is counted towards the original flow already obtained.
Triggers - concurrent requests

  • Synchronous: 100 concurrent requests per message pack for a service instance that includes a new license and 400 concurrent requests per message pack for a service instance that uses an existing license (BYOL), up to a maximum of 2,000 (for 20 message packs)

    Increasing the concurrent request limit with additional message packs is useful if you have high concurrency requirements in respect to synchronous integration executions.

    For details about how concurrent request scalability is calculated, see Message Pack Usage and Synchronous/Asynchronous Requests.

    Parallel action branches independent of the integration type (synchronous, asynchronous, and so on) count towards the concurrency limits on synchronous requests.

    For example, a parallel action with three branches needs two extra concurrency slots for the duration of the parallel action; one branch is counted towards the original flow already obtained.

  • Asynchronous: No limit; the following number of requests can execute at a time, the rest are queued; 50 requests per message pack for a service instance that includes a new license and 200 requests per message pack for a service instance that uses an existing license (BYOL), up to a maximum of 1,000 (for 20 message packs)

    Asynchronous concurrent execution includes scheduled + triggered + connectivity agent.
Event integrations (integrations that can subscribe to events)
  • 50 integrations per service instance
Tracking events (per single integration instance/request execution)
  • Non-error events: 20,000
  • Error events: 30,000 (extra 10,000 if events are associated with errors)
  • Maximum errors recorded: 2,000

After those limits are reached, events are no longer recorded in the activity stream, but they continue to be processed, and the integration instance overall state is calculated. This ensures that the integration instance state is updated in all scenarios.
Integration flow duration

  • Synchronous: 5 minutes

    After that, an HTTP 502 occurs.

  • Asynchronous: 6 hours

    After that, the integration instance is marked as aborted due to deadline timeout.

  • Scheduled: 6 hours

    After that, the integration instance is marked as aborted due to deadline timeout.
Stage file action (in integrations) limits
  • Read Entire File operations: 100 MB

    For files greater than 100 MB, use the Read File in Segments operation.

  • Encrypt File operations: 1 GB
  • Decrypt File operations: 1 GB
Synchronous integration message timeout

  • 300 seconds

    After that, the integration returns a timeout error.
Oracle Integration Messaging message size
  • 10 MB
Encode and decode file attachment content (mapper)
  • 10 MB for encodeReferenceToBase64(String reference) and decodeBase64ToReference(String base64Content) functions
Lookups
  • Maximum number of rows in lookup table: No limit
  • Maximum number of columns in lookup table: 100
  • Maximum lookup import limit: 100 MB
  • Maximum column length: 2,048 characters
  • Domain name length: 50 characters
Notification action limits

  • Default method: 500 KB maximum email body size (cannot be exceeded)

    The email body size and attachment size are both considered in calculating the total size for the default method. The maximum total size for the default method is 2 MB. For example, if the email body size of your message is 250 KB, you can attach files of up to 1.75 MB in encoded size to reach the total default value of 2 MB.

  • Customer tenancy method: 500 KB maximum email body size (cannot be exceeded)

    The email body size and attachment size are both considered in calculating the total size for the customer tenancy method. The total size can be increased until the maximum value supported by the Oracle Cloud Infrastructure Email Delivery Service is reached.

    For example, assume the total size supported by your customer tenancy is 4 MB. If the email body size of your message is 250 KB, you can attach files of up to 3.75 MB in encoded size to reach the total customer tenancy value 4 MB.

See Configure Notification Emails and Email Delivery Service Capabilities and Limits.

Outbound emails (sent from Oracle Integration in a rolling 24-hour window)
  • Default method: 10,000 emails
  • Customer tenancy method: The limit is the number allowed by the Oracle Cloud Infrastructure Email Delivery Service.

See Configure Notification Emails and Email Delivery Service Capabilities and Limits.

JavaScript execution timeout
  • 15 seconds
JavaScript function parameters
  • 20 parameters
XSLT execution duration
  • 120 seconds
Scheduled integrations - concurrent requests

  • Scheduled or out-of-band: 1

    An out-of-band request is a run now run associated with a schedule.

  • Ad-hoc: 1

    An ad-hoc request is a run now run not associated with a schedule.

Tenant and user requests
  • User interface: 100 requests per second per tenant and 20 requests per second per user
  • Observability (instances/errors) API: 50 requests per second
Schedule integrations - long-running integration duration
Loop iterations

  • While loop: 5,000 iterations

  • For-each loop: No limit

  • Tracked loop iterations: 1,000 iterations

    Maximum number of iterations captured across all loops for a single instance ID for which tracking data is captured.
Project limits (maximum per project)
  • Integrations: 200
  • Connections: 100
  • Lookups: 100
  • JavaScript libraries: 50
  • Deployments: 100
  • Queues: 50
  • Events: 50
Parallel action branches
  • 5 branches
Tracking variable value character limit
  • 8,191 characters
Maximum number of global variables
  • 20
Service instance data retention Retention is based on the trace level set during integration activation:
  • Production: 32 days (default) for Standard and Enterprise editions, 184 days for Healthcare edition

    You can increase the data retention period for Standard and Enterprise editions if you want. See Edit the Data Retention Period.

  • Audit: 8 days
  • Debug (Not Recommended): 24 hours

    Note: After 24 hours, Debug (Not recommended) is automatically reset to Production. See Activate an Integration in Using Integrations in Oracle Integration 3.

Time window for recovering a failed integration instance that's recoverable The integration instance is recoverable until one of the following occurs:
  • It's aborted. This can happen due to integration deactivation.
  • It's successfully recovered or the recovery leads to a nonrecoverable error.
  • It's beyond its associated retention time, which is 32 days (default) for Standard and Enterprise editions, 184 days for Healthcare edition.
Activity stream - displayable rows
  • 5,000 rows (when expanding the tree)
Activity stream - total size (REST response)
  • No limit
Integration instances returned per monitoring request
  • 50 instances
Resubmissions allowed per integration instance ID
  • 10 resubmissions
Schedule parameter values character limit
  • 256 characters
Schedule parameters per integration
  • 5 parameters
Integration property values character limit
  • 256 characters
Integrations and connections character limits
  • Name: 50 characters
  • Package name: 50 characters
  • Version: 10 characters
  • Description: 1,024 characters
Maximum offset supported (Instances and Errors API)
  • 500
Maximum limit supported (Instances and Errors API)
  • 50
Developer API for Oracle Integration 3 timeout
  • 2 minutes
Payloads for publishing and subscribing to events in integrations
Activity stream payloads

  • 32 KB per payload

    Payloads larger than 32 KB are stored in the Object Store. There is no limit for payloads stored in the Object Store.

  • 25 MB total per integration instance
Oracle Cloud Infrastructure API Gateway limits
  • 20 deployments per gateway
  • 50 routes per deployment

This allows for a total of 1,000 integration endpoints per gateway.
B2B for Oracle Integration - Trading partner management and B2B message tracking See Manage Trading Partners and Track B2B Messages in Using B2B for Oracle Integration 3.