Concurrency limit reached

How to recognize it

The API answers with status 429 and a JSON body with the message and the error.code concurrency_limit_exceeded, for example:

HTTP/1.1 429
Content-Type: application/json

{
  "error": {
    "code": "concurrency_limit_exceeded",
    "message": "Your plan renders 2 screenshots at the same time and is at that limit now. Please retry when one is done, or upgrade your plan to render more at once."
  },
  "message": "Your plan renders 2 screenshots at the same time and is at that limit now. Please retry when one is done, or upgrade your plan to render more at once."
}

Common causes

• More requests at once than your plan renders at the same time: 2 on the free plan, 5 on Basic, 10 on Premium, more on Enterprise.
• With async=true: 10 times that number of jobs already queued or rendering (Your plan may have 50 async jobs queued or rendering at the same time and is at that limit now.).

How to fix it

1. Wait for the Retry-After header and send it again, or queue your requests so that fewer run at once.
2. Upgrade the plan to render more at once.

Retry

After the seconds in Retry-After.

Billing

Not billed: a request answered with this error does not count against your quota.

Every response carries an X-Request-Id header. If this page does not explain the error, write to support@screenshotbase.com with that id. All statuses: status codes.