Oracle Primavera · Rate Limits

Oracle Primavera Rate Limits

Oracle Primavera REST APIs (P6 EPPM, Gateway, Analytics, Scheduling) do not publish per-second or per-minute rate-limit numbers. Throughput on Primavera Cloud is bound by the underlying multi-tenant pod capacity; on-premises P6 EPPM throughput is bound by the customer-deployed application server (Oracle WebLogic) and database tier. Bulk operations are typically routed through Primavera Gateway with its own batch and pagination patterns.

Oracle Primavera Rate Limits is the machine-readable rate-limit profile for Oracle Primavera on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring varies and concurrent_jobs.

The profile also includes 4 backoff/retry policies defined and response codes documented for unauthorized, forbidden, notFound, serverError, and serviceUnavailable.

Tagged areas include Project Management, Oracle Cloud, Rate Limiting, and Scheduling.

3 Limits
Project ManagementOracle CloudRate LimitingScheduling

Limits

REST API Throughput (Primavera Cloud) tenancy
varies
bound by Primavera Cloud pod capacity
Throughput is governed by the underlying Primavera Cloud pod and is not exposed as a public per-tenancy rate-limit table.
REST API Throughput (P6 EPPM On-Premises) deployment
varies
bound by deployed WebLogic / database capacity
Throughput is governed by the customer-deployed Oracle WebLogic application server and Oracle Database tier hosting P6 EPPM.
Gateway Batch Job Concurrency deployment
concurrent_jobs
see Primavera Gateway Administration Guide
Concurrent batch synchronization jobs are configured per Primavera Gateway deployment.

Policies

Capacity-Bound Throttling
Throughput limits are determined by deployment sizing (Primavera Cloud pod or on-premises WebLogic / database) rather than a published per-tenancy rate-limit table.
Backoff Strategy
Clients should implement exponential backoff with jitter on 5xx responses; honor any Retry-After header when present.
Bulk Patterns
For bulk synchronization with ERP, finance, or BIM systems prefer Primavera Gateway adapters over hitting transactional REST endpoints.
Pagination
Use the documented pagination parameters on collection endpoints and avoid issuing parallel large List operations.

Sources