Adobe Launch · Rate Limits

Adobe Launch Rate Limits

Adobe Launch has two surfaces with completely different rate-limit postures. The Edge Network data collection endpoints carry real, published, numeric guardrails expressed in "request units". The Reactor management API carries none — Adobe publishes no numeric limit, no response headers and no 429 for it, only a note that a 500 may indicate throttling.

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

It captures 4 rate-limit definitions, measuring request units per second and bytes.

The profile also includes 2 backoff/retry policies defined and response codes documented for documented_throttle_status and note.

Tagged areas include Rate Limiting, Tag Management, Experience Platform, and Edge Network.

4 Limits
Rate LimitingTag ManagementExperience PlatformEdge Network

Limits

Edge Network — interact datastream
request units per second
4000
Edge Network — collect datastream
request units per second
6000
Edge Network — HTTP request size request
bytes
65536
Reactor API unknown

Policies

Backoff strategy
With no Retry-After and no 429, the only workable client strategy is exponential backoff with jitter on 5xx.
Build pipeline pacing
Library builds are asynchronous. Poll getBuild rather than retrying createBuild, which would queue duplicate builds.