#nimheru_error
gray mulchBOT
đ 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/1293229570140405885
đ 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.
- nimheru_docs, 6 days ago, 6 messages
main token
Is there a better way to find info on these errors or is this the extent of the data available to us?
I did post an example request ID above but here's anohter if it's any use! req_WoQdzLLslTBzYS
foggy wren
Hello
Taking a look
Okay yeah looks like we had a bug from about 14:26 - 14:30 UTC today that caused a lot of requests to 500. This was an issue on our end but was quickly fixed.
We talk about how to handle when this happens in our docs here: https://docs.stripe.com/error-low-level#server-errors
main token
Oh ok great thanks, wasn't sure if I was missing something