Introducing a Platform-Wide Throughput Limit

Benchling is introducing a tenant-wide data throughput limit to the Developer Platform on November 27th. Tenants that have integrations or scripts creating or updating objects in the tens of thousands per hour may experience 429 rate limit errors. Expand for more details.

What’s changing?

Benchling is introducing a tenant-wide data throughput limit to the Developer Platform to protect the stability and performance of our internal systems. A throughput limit is a limit on the total amount of data being created or updated in Benchling over a period of time. While Benchlings’s data and rate limits (found on the Limits page) outline restrictions on the size and frequency of individual API requests, the throughput limits discussed here outline restrictions that apply across many requests over the course of hours.

The throughput limit is enforced dynamically based on the total number of objects (e.g. entities, containers, results, etc.) that are created or updated over a given period of time. The exact point at which the throughput limit is enforced may change in response to system load, but it will generally allow for creating or updating tens of thousands of objects per hour.

Creating or updating large numbers of objects too quickly may result in hitting the throughput limit, resulting in HTTP 429 rate limit errors. The recommended best practice for handling these errors is to implement an exponential backoff strategy for retrying the requests.

When is this happening?

The throughput limit will be implemented on November 27th. The majority of Benchling tenants ingest data at a rate well below the throughput limit threshold, and therefore should not notice any changes. The small number of Benchling tenants that ingest data at rates that may result in hitting the throughput limit will be contacted directly.

If you have questions or concerns about hitting the throughput rate limit, please reach out to your Benchling Account Executive or Customer Success Manager.