#vilesa-ratelimit
1 messages · Page 1 of 1 (latest)
@livid gust there wouldn't be a request ID in that case, the 429 gets returned at a point earlier in the stack than before the request starts getting processed and generates an ID
what are you really trying to do or to find the answer to?
thanks!
I am seeing some rate limiting that seems to be minute based rather than second based (and the docs only describe second based rate limiting). And I wanted to capture a request ID to communicate to you for you to confirm why the request generated a RateLimitError
probably better to write in with the exact UTC timestamps when you saw limiting. It's easy enough for us to look at your logs