#vlad_webhooks
livid aspenBOT
đ 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/1328474087651020964
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- vlad_api, 4 days ago, 16 messages
marble pastureBOT
winged vigil
We don't document this
You can assume it could change
Our advice is just to respond with a 200 as quickly as possible and to not do any heavy processing synchronously
If you need to do heavy processing, use a job queue, then queue up the event and respond with a 200
buoyant sphinx
The issue that we've noticed that some of our requests are marked timed out, but per our logging it didn't take more than 5-6s to process
Can we safely assume that everything under 10-15s is fine?