#tymm_unexpected
1 messages · Page 1 of 1 (latest)
👋 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/1354273672420134994
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
this is a screenshot in prod from our customer
and when i tried it in our test env yesterday i see this too after performing this: req_HtAQfdQB4HImnL
We have identified this issue yesterday and the fix has been done.
This issue should have been resolved now
can i know what happened
I’m afraid I don’t have the context of why this happened. Can I suggest you writing to support https://support.stripe.com/contact, so that they can follow up with you?