Service Limits

Review the following service limits for Oracle Integration 3 resources. A service limit is the quota or allowance set on a resource. You cannot change the service limits configured for your tenancy.

Note:

The service limits described below are enforced.

Oracle Cloud Infrastructure Console Service Limits

For more Oracle Cloud Infrastructure Console service limits, see Service Limits in the OCI documentation.

Resource	Service Limit
Integration service instances	200 service instances per region Note: This value is the number of service instances you provision per region, and not the number of integration instances (for example, application and schedule) that you activate and monitor under the Observability tab in Oracle Integration. The ability to create service instances outside your home region depends on several factors. See Restrictions.
Private endpoints	1 private endpoint per service instance 1 subnet per private endpoint
Custom endpoints	1 custom endpoint per service instance
Oracle Integration internal diagnostic logs	30 days - retained in Oracle Cloud Infrastructure Logging for debugging use See Log Analytics.

Component: Adapters

Resource	Service Limit
Connectivity agent memory	A minimum of 8 GB memory with 4 GB of heap size dedicated to the on-premise agent's Java Virtual Machine (JVM). To include any other processes on the host besides the agent, increase the physical memory to a value greater than 8 GB.
Connectivity agent message payloads	10 MB through the use of compression All connectivity-agent-enabled adapters 50 MB as request 50 MB as response SOAP and REST adapters configured with connectivity agent 50 MB (structured XML/JSON document) as response from SOAP/REST endpoints 1 GB for attachments as part of a response from SOAP/REST endpoints
Structured payloads (JSON, XML) for connectivity-agent-based adapters	SOAP and REST: 50 MB File and FTP invoke responses: 50 MB Other protocols: 10 MB (for example, database, JMS, MQ, Kafka, and others)
Structured payloads for trigger connections and responses from invoke connections	Cloud endpoints: 100 MB (not using the connectivity agent) Private endpoints: 100 MB
Binary (unstructured) payloads (for example, attachments, MTOM) for trigger connections and responses from invoke connections	1 GB
Private endpoint support	Connecting to private endpoints is supported in a growing list of adapters. See Adapters that Support Connecting to Private Endpoints in Using Integrations in Oracle Integration 3.
Apache Kafka Adapter	For invoke configurations Produce/Consume Message operations: 10 MB with schema transformation for all the outbound operations
AS2 Adapter	100 MB
Database adapters Oracle Autonomous Data Warehouse Adapter Oracle Autonomous Transaction Processing Adapter Oracle Database Adapter Oracle Database Cloud Service Adapter IBM DB2 Adapter Microsoft SQL Server Adapter MySQL Adapter Netezza Adapter PostgreSQL Adapter SAP ASE (Sybase) Adapter Snowflake Adapter	For trigger configurations Polling operations: 50 MB with schema transformation for agent-based endpoints 100 MB with schema transformation through private endpoints For invoke configurations Stored Procedure, Operation on Table, and Run PureSQL Statement operations: 10 MB with schema transformation for all the outbound operations Database Select operations: 100 MB for public internet-based endpoints 100 MB for private endpoints 50 MB for agent-based endpoints
File Adapter (available only with the connectivity agent)	Read File operations: 1 GB when used without a schema 50 MB when using a schema for transformation 50 MB for a read operation with structured payload Polling with a connectivity agent: 50 MB Download File operations: 1 GB Note: The size of CSV files increases when translated into a message. Therefore, the file size must be less than 50 MB, so that the after-translation message size does not exceed 50 MB.
FTP Adapter	For invoke configurations Read File operations: 1 GB when used without a schema (when used with or without a connectivity agent) 100 MB for cloud-based endpoints when using a schema for transformation 50 MB for agent-based endpoints when using a schema for transformation 100 MB for public internet-based endpoints 100 MB for private endpoints Download File operations: 1 GB (when used with or without a connectivity agent) Write File operations: There is no limit
JMS adapters Oracle WebLogic JMS Adapter IBM MQ Series JMS Adapter	For trigger configurations Consume Message operations: 10 MB with schema transformation For invoke configurations Produce Message operations: 10 MB with schema transformation
Oracle CPQ Adapter	50 MB for response payloads
Oracle E-Business Suite Adapter	100 MB for public internet-based endpoints 50 MB for agent-based endpoints
REST Adapter	For trigger configurations 3 MB for XML documents used for schema generation See REST Adapter Capabilities. 1 GB for messages with attachments (for example, multipart/form-data) 100 MB for incoming structured message payloads (any content-type header containing JSON, XML, HTML, YAML, or YML) Note: If the string length for fields in a JSON payload exceeds 20 MB, you receive a translation failure error. See ORABPEL-15235 Translation Failure Occurrence in Using the REST Adapter with Oracle Integration 3. 1 GB for incoming content as raw bytes (application/octet-stream as content type) 100 KB for JSON sample files used to specify the response payload format in the Adapter Endpoint Configuration Wizard For invoke configurations 3 MB for XML documents used for data definition generation See REST Adapter Capabilities. 100 KB for JSON sample files used to specify the request payload format in the Adapter Endpoint Configuration Wizard 1 GB for responses returned as part of invoke runtime binary data (application/octet-stream) 50 MB for responses returned from agent-based endpoints for structured content (for example, JSON/CSV/XML, and so on) 100 MB for responses returned from private endpoints for structured content (for example, JSON/CSV/XML, and so on) 100 MB for responses returned from public internet-based endpoints for structured content (for example, JSON/CSV/XML, and so on)
REST-based adapters (adapters that expose REST endpoints on the inbound or adapters invoking external REST endpoints) For example, Oracle Commerce Cloud Adapter, Oracle Fusion Field Service Adapter, and so on.	For trigger configurations (wherever applicable) 3 MB for XML documents used for schema generation See REST Adapter Capabilities. 1 GB for messages with attachments (for example, multipart/mixed and multipart/form-data) 100 MB for incoming structured message payloads (any content-type header containing JSON, XML, HTML, YAML, or YML) 1 GB for incoming content as raw bytes (application/octet-stream as content type) 100 KB for JSON sample files used to specify the response payload format For invoke configurations (wherever applicable) 3 MB for XML documents used for data definition generation See REST Adapter Capabilities. 1 GB for attachments in outbound requests 100 KB for JSON sample files used to specify the request payload format 50 MB for agent-based endpoints 100 MB for private endpoints 100 MB for public internet-based endpoints
Salesforce Adapter	8 MB per batch (10,000 records) See Process Large Data Sets Asynchronously with Different Bulk Operations.
SAP Adapter	50 MB For the SAP Adapter as a trigger connection, the limit is 50 MB for all document types.
SAP Ariba Adapter	See SAP Ariba Adapter Restrictions.
SOAP Adapter	For trigger configurations 100 MB for structured payloads (XML) in requests and responses For invoke configurations 100 MB for structured payloads (XML) in requests and responses 50 MB for agent-based endpoints 100 MB for private endpoints 100 MB for public internet-based endpoints
SOAP-based adapters (adapters that expose SOAP endpoints on the inbound or adapters invoking external SOAP endpoints) For example, Oracle Logistics Adapter.	For trigger configurations (wherever applicable) 100 MB for structured payloads (XML) in requests and responses For invoke configurations (wherever applicable) 100 MB for structured payloads (XML) in responses 50 MB for agent-based endpoints 100 MB for private endpoints
Connectivity-agent-based outbound adapter invocation timeout	4 minutes for connection timeout
Outbound adapter invocation timeout	READ timeout: 5 minutes Connection timeout: 5 minutes
Integration timeout for: Oracle Autonomous Data Warehouse Adapter Oracle Autonomous Transaction Processing Adapter Oracle Database Cloud Service Adapter MySQL Adapter Microsoft SQL Server Adapter Oracle Database Adapter IBM DB2 Adapter	240 seconds Any integrations created after August 2021 that include stored procedure or PureSQL database operations will time out after this limit.

Component: Integrations

Resource	Service Limit
Active integrations	800 active integrations See Activate an Integration in Using Integrations in Oracle Integration 3.
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	10,000 characters This limit applies to all variables of type string, including global variables, and all functions, including concat functions used inside an assign, stitch, or mapper.
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, up to a maximum of 2000 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, up to a maximum of 1000 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 character limit: 1,024 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	6 hours After that, the integration is terminated by Oracle Integration. See When a Schedule Integration Instance Gets Terminated in Using Integrations in Oracle Integration 3.
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
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 for an Instance. 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	The same limit supported by the inbound (trigger) adapter. See Component: Adapters.
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.

Component: Robotic Process Automation

Resource	Service limit
Robot instance duration	4 hours
Assigning a robot instance to an environment timeout	Varies, depending upon the environments: If the environment pool contains no environments: 0 seconds, and then the status of the robot instance changes to Failed If the robot agent on the environment doesn't accept the request: 30 seconds, and then Oracle Integration attempts to assign the robot instance to a different environment If all environments in the environment pool have a status of Unavailable: 240 seconds, and then the status of the robot instance changes to Failed If at least one environment in the environment pool has a status of Available: No limit
File download timeout	180 seconds by default but the robot builder can specify a different value while creating a robot
File download size	50 MB
Polling frequency (frequency at which the robot agent polls Oracle Integration for work)	15 seconds
Maximum time that Oracle Integration waits for the robot agent to poll for work before changing its environment's status to Unavailable	35 seconds
Service instance data retention	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 for an Instance. Audit: 8 days Debug (Not Recommended): 24 hours After 24 hours, a robot instance's Debug tracing level automatically changes to Production.
Environments in an environment pool	100 environments
Robot character limits	Name: 50 characters Description: 1,024 characters Keywords: 1,024 characters
Environment pool character limits	Name: 50 characters Description: 1,024 characters Keywords: 1,024 characters
Robot connection type character limits	Name: 50 characters Description: 1,024 characters Keywords: 1,024 characters
Robot connection character limits	Name: 50 characters Description: 1,024 characters Keywords: 1,024 characters

Component: File Server

Resource	Service Limit
Storage	500 GB
Concurrent connections	50 connections per service instance

Component: Decisions

Decision application service limits in a project

Resource	Service limit
Maximum number of decision applications per project	10
Maximum number of decision applications across all projects	100
Maximum number of versions that can be created per decision application	25
Maximum number of activated versions per decision application	10

Service limits for a decision model

Resource	Service limit
Maximum number of concurrent executions for mutating PUT/PATCH/DELETE operations in Decision Lifecycle APIs	1
Maximum number of decision nodes per decision model	50
Maximum number of rules (rows) per decision table	100
Maximum number of input expressions (columns) per decision table	15
Maximum number of key/value pairs per context decision	50
Maximum number of conditions in if/else and nested if/else	100
Maximum number of entries (row x column) in relation table	200
Maximum number of input data per decision model	20
Maximum number of business types per decision model	20
Maximum number of services per decision model	10
Maximum number of levels in nested decisions	2

Component: Process Automation

For Process Automation service limits, see Service Limits in Administering Oracle Cloud Infrastructure Process Automation.

Message Pack Usage and Synchronous/Asynchronous Requests

The following table shows the concurrent request limits based on the number of message packs you've subscribed to.

Message Packs Assigned	Synchronous Request Limit	Asynchronous Request Limit
20	2000	1000
19	1900	950
18	1800	900
17	1700	850
16	1600	800
15	1500	750
14	1400	700
13	1300	650
12	1200	600
11	1100	550
10	1000	500
9	900	450
8	800	400
7	700	350
6	600	300
5	500	250
4	400	200
3	300	150
2	200	100
1	100	50

Note:

With version 25.06, the ceiling was moved from 6 message packs assigned to 20 message packs assigned. This ceiling may be subject to change.

When to Increase Message Packs

You might need to increase message packs in the following situations:

Situation	Reason to increase	Example
You're consuming more messages than you subscribe to.	Your message packs should equate to the number of messages your Oracle Integration instance consumes per hour. Therefore, it's essential that you know your instance's hourly throughput, and increase your message packs as necessary to match the throughput.	You have 2 message packs, giving you 10,000 messages per hour, which covers your average throughput. Your requests usually take about 5 seconds to complete, so you process 12 requests per minute: 60 seconds per minute / 5 seconds per request = 12 requests per minute You average 10 concurrent synchronous requests, so now you're up to 120 concurrent requests per minute: 12 requests per minute x concurrency of 10 = 120 concurrent requests per minute That means you generally process 7,200 requests per hour: 120 concurrent requests per minute x 60 minutes = 7,200 requests per hour We'll say that each request consumes one message, so you normally consume 7,200 messages per hour, which falls under your message pack subscription. But sometimes you get a 10-minute burst of 100 concurrent synchronous requests. You're suddenly processing 10 times as many requests—1,200 requests per minute, for a total of 12,000 requests during the burst. When you add that to your average messages for the rest of the hour, you've consumed 18,000 messages: 50 average minutes x 120 requests per minute = 6,000 requests 6,000 requests + 12,000 request burst = 18,000 requests That puts you 8,000 messages over your message pack subscription: 10,000 subscribed messages - 18,000 consumed messages = 8,000 message overage You would need to subscribe to 2 more message packs to handle your request bursts.
You need to handle bursts of high concurrency.	The number of message packs directly affects the concurrent synchronous (and asynchronous) request limit.	You have 2 message packs, allowing you up to 200 concurrent synchronous requests. You average a concurrency of 25, so you're usually well within that limit. But sometimes you get a burst of 250 concurrent synchronous requests. Since that exceeds your limit, the extra requests get errors. You would need to subscribe to 1 more message pack to handle your request bursts.