-
### Type of feature
💡 Feature
### Current behavior
I sometimes get
You have exceeded a secondary rate limit. Please wait a few minutes before you try again. If you reach out to GitHub Support fo…
-
![Untitled](https://github.com/user-attachments/assets/69046cd0-7a94-4500-86b4-db1f8208d25a)
-
### Component(s)
_No response_
### Is your feature request related to a problem? Please describe.
We run an observability backend (Elasticsearch) shared by many teams and services (thousands)…
-
It seems that some providers, e.g. RedHat do some rate limiting and also limit concurrent connections.
-
If you exceed your Screenscraper account rate limit for the day, the following error will be found in the log file:
` ERROR - Error making HTTP request: 430 Client Error: for url: https://api.scre…
-
To avoid spam (as we got recently) we can add a rate limiting to messages and a ban policy if the limit is exceeded.
The detection of a misbehaving user is done at the domain layer (chat) and we c…
-
This is necessary for apify/crawlee-python#60 to bring benefit to running crawlee on Apify
Rate limit errors should have status code 429 (please recheck)
-
Several customers have asked for support for basic composition with rate limiters, e.g. (limit1 AND limit2 AND limit3). Imagine a scenario where a service has an official rate limit of "10 per second,…
-
### Describe the bug
When i am creating connected accounts too quickly, i get an error with an HTTP status code of 400:
```ts
logger.error(error as Stripe.errors.StripeAPIError);
logger.error(…
-
Hi, I believe i have just gotten rate limited (axios all of a sudden gives a 429 "Too Many Requests" Error when everything was working before and there have been no changes to the code).
I read in…