Skip to main content
This page is the resolution target of the RFC 9457 type URI on every too_many_streams problem body: https://docs.get-exo.com/errors/too_many_streams. HTTP status: 429 Too Many Requests.

Why it happens

GET /v1/events holds a long-lived connection and a subscription for as long as it is open. The cap is five concurrent streams per organization, counted across all members and all credentials. This is a separate limit from the ordinary rate limiter. A stream that is open costs nothing per second, so the constraint is concurrency rather than throughput.

How to fix it

  • Close streams you are no longer reading. A slot is released as soon as the connection ends.
  • Do not open one stream per browser tab. Open one and fan out inside your own application.
  • If you need durable delivery to many consumers, register a webhook instead. Webhooks have no concurrency cap of this kind.