Skip to content

Commit 47d7b75

Browse files
authored
Update limits.mdx
1 parent ffd78a5 commit 47d7b75

File tree

1 file changed

+5
-2
lines changed
  • src/content/docs/browser-rendering/platform

1 file changed

+5
-2
lines changed

src/content/docs/browser-rendering/platform/limits.mdx

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ The limits for Browser Rendering will continue to be raised over time. In the me
4646
| Browser timeout | 60 seconds |
4747
| Total requests per min (REST API only) | 180 per minute [^2] [^3] |
4848

49-
[^2]: Rate limits are enforced with a fixed **per-second fill rate**. For example, a limit of 180 requests per minute translates to **3 requests per second**. This means you cannot send all 180 requests at once; the API expects them to be spread evenly over the minute. If your account has a custom higher limit, it will also be enforced as a per-second rate.
49+
[^2]: Rate limits are enforced with a fixed **per-second fill rate**. For example, a limit of 180 requests per minute translates to **3 requests per second**. This means you cannot send all 180 requests at once; the API expects them to be spread evenly over the minute. If your account has a custom higher limit, it will also be enforced at a per-second rate.
5050
[^3]: Contact our team to request increases to this limit.
5151

5252
:::note[Note on browser timeout]
@@ -84,7 +84,10 @@ If you recently upgraded to the [Workers Paid plan](/workers/platform/pricing/)
8484

8585
### Error: `429 Too many requests`
8686

87-
When you make too many requests in a short period of time, Browser Rendering will respond with HTTP status code `429 Too many requests`.
87+
When you make too many requests in a short period of time, Browser Rendering will respond with HTTP status code `429 Too many requests`.
88+
89+
Rate limits are enforced with a fixed **per-second fill rate**. For example, a limit of 180 requests per minute translates to **3 requests per second**. This means you cannot send all 180 requests at once; the API expects them to be spread evenly over the minute. If your account has a custom higher limit, it will also be enforced at a per-second rate.
90+
8891
The response includes a `Retry-After` header, which specifies how many seconds to wait before retrying. You can view your account's rate limits on the [Limits](/browser-rendering/platform/limits/) page.
8992

9093
The example below demonstrates how to handle rate limiting gracefully by reading the `Retry-After` value and retrying the request after that delay.

0 commit comments

Comments
 (0)