Informatica · Rate Limits

Informatica Rate Limits

Informatica IDMC governs throughput primarily via the IPU consumption ceiling and per-service Secure Agent / runtime concurrency limits rather than published per-second HTTP rate limits. API & App Integration processes have configurable concurrency on the Cloud Server runtime; mass ingestion and data integration jobs scale by Secure Agent capacity. Specific per-second TPS values are tenant- and pod-dependent.

2 Limits Throttle: 429

Data IntegrationiPaaSIDMCRate Limiting

Limits

IDMC API throughput org

varies

governed by Secure Agent capacity, runtime concurrency, and IPU consumption ceiling

Cloud Application Integration process concurrency org

concurrent_processes

configurable on the Cloud Server / Secure Agent runtime

Policies

Backoff Strategy

Clients receiving 429 or 503 should implement exponential backoff with jitter and honor Retry-After when present.

IPU Consumption Alerting

Set IPU consumption thresholds in the IDMC admin UI to receive alerts before pool exhaustion throttles new job submissions.

Runtime Sizing

Throughput is bounded by Secure Agent / runtime sizing; scale by adding agents or moving to a Cloud Server runtime.

Fair Use

Informatica reserves the right to throttle traffic that materially impacts shared pod infrastructure.