#matt-k_webhooks
dire mantleBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1362161472003772747
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
golden relic
We aren't sure if a user did hit a rate limit, we're just wanting to build out monitoring in case we do hit a rate limit
fallen badger
Gotcha, then no, no Events are generated if a request hits a rate limit (429) error.
golden relic
What's typically the best way to surface users receiving these error in browser?
Would we need to record response data ourselves?
fallen badger
Yeah you would show your own error message or you would queue the requests on your side and try them again shortly afterward.
So you could show a spinner to your customer or something like that while waiting for the requests to process.
Really up to you
golden relic
Ok thanks!!