Oracle Integration · Rate Limits

Oracle Integration Rate Limits

Oracle Integration enforces per-instance service limits rather than a per-second / per-minute rate-limit table. Throughput scales with the provisioned edition and message-pack count; structural caps apply to active integrations, payload sizes per adapter, scheduled-instance concurrency, loop iterations, file-server storage, and outbound notifications. Lifecycle operations against the underlying OCI control plane inherit the standard OCI service-limits envelope. The numbers below come from the Oracle Integration Service Limits documentation.

24 Limits Throttle: 429
API ManagementCloud IntegrationiPaaSOracle CloudRate Limiting

Limits

Integration Service Instances per Region tenancy/region
instances
200
Maximum number of Oracle Integration service instances per OCI region.
Custom Endpoints per Instance instance
endpoints
3
Up to three alternative custom endpoints per Oracle Integration instance.
Active Integrations per Instance instance
integrations
700
Maximum number of activated integrations per Oracle Integration instance.
Synchronous Integration Timeout integration
seconds
300
Hard timeout for synchronous integration invocations.
Long-Running Scheduled Integration Limit integration
hours
6
Maximum runtime for a single scheduled integration execution.
Concurrent Scheduled Instances integration
concurrent_instances
2
One scheduled / out-of-band instance plus one ad-hoc instance per scheduled integration.
For-Each Loop Iterations integration
iterations
5000
Maximum iterations per for-each loop within an integration.
While Loop Iterations integration
iterations
5000
Maximum iterations per while loop within an integration.
Activity Executions per Instance integration
activity_executions
1000
Maximum activity executions per integration instance.
Structured Payload (Cloud Endpoints) request
payload_size_bytes
52428800
50 MB structured payload limit for cloud-endpoint adapters.
Binary / Attachment Payload (Cloud Endpoints) request
payload_size_bytes
1073741824
1 GB binary, attachment, or MTOM payload limit for cloud-endpoint adapters.
Connectivity Agent Payload (SOAP / REST) request
payload_size_bytes
52428800
50 MB payload limit for SOAP and REST adapters routed through the connectivity agent.
Connectivity Agent Payload (Database / JMS / MQ / Kafka) request
payload_size_bytes
10485760
10 MB payload limit for Database, JMS, MQ, and Kafka adapters via the connectivity agent.
AS2 Adapter Payload request
payload_size_bytes
10485760
10 MB AS2 adapter payload limit.
Salesforce Adapter Batch request
records
10000
8 MB / 10,000-record batch limit for the Salesforce adapter.
Stage File - Read Entire File integration
payload_size_bytes
10485760
10 MB cap when using Stage File "read entire file" mode.
Stage File - Encrypt / Decrypt integration
payload_size_bytes
1073741824
1 GB cap when using Stage File encrypt or decrypt operations.
Activity Stream Size instance
bytes
104857600
100 MB activity stream cap; payloads are truncated at 512 KB within the stream.
File Server Storage instance
GB
500
500 GB total file-server storage per Oracle Integration instance.
File Server Concurrent Connections instance
concurrent_connections
50
50 concurrent SFTP / file-server connections per Oracle Integration instance.
Daily Outbound Emails instance
emails_per_day ยท day
10000
10,000 outbound notification emails per day per instance.
JavaScript Action Timeout integration
seconds
15
15 second per-invocation timeout for JavaScript actions.
JavaScript Function Parameters integration
parameters
20
Up to 20 parameters per JavaScript function.
OCI Control-Plane Operations tenancy
requests_per_second
see OCI service-limits documentation
Lifecycle operations (create, update, scale, delete instance) inherit the standard OCI control-plane throttling envelope.

Policies

Hard Service Limits
The numeric limits above are enforced by Oracle Integration and cannot be increased on a per-tenant basis. Solutions exceeding a limit must be redesigned (split integrations, larger edition, additional message packs, or migrate to bulk patterns).
Capacity Scaling
Throughput is scaled by adding message packs to the instance or moving to a higher edition (Standard, Enterprise, Healthcare); raise a service request to expand the per-region instance count beyond 200.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 / 5xx responses; honor any Retry-After header when present.
Bulk Patterns
For high-volume integrations prefer scheduled / batch integrations with chunking and the File Server staging pattern over synchronous REST invocations.
Connectivity Agent Sizing
Where on-premises adapters are used, ensure the connectivity agent host has the required 8 GB minimum (4 GB heap) to avoid client-side throttling.

Sources