#warhost_unexpected
stiff pikeBOT
👋 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/1483385838380515328
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
torpid vapor
red pagoda
hi there!
torpid vapor
Hello 👋
red pagoda
can you share the Request ID (req_xxx) that is shown in your screenshot?
torpid vapor
Just reproduced it fresh for you: req_YVpcZx2wxB77mt
red pagoda
thanks! so in this specific case you would have liked the error message to be shown directly on the embedded component, instead of the generic "an unknown error has occured"?
torpid vapor
yes exactly. Because this is information that's very valuable to the user and there is nothing as platform that we can do about this.
It's also not jus this one error, I believe there are more that are unmapped / resulting in "unknown error" while the console shows a valuable error message. One example is when the connected accounts account is low in funds and a refund is trying to be initiated.
It's just I can't reproduce them right now.
"unkown error" is just misleading, it's a known error, just the frontend component isn't aware of it. I believe the component should just show the message from the API response, since the message is in the browser anyway, there is nothing to hide.
red pagoda
yes, I agree with you. I can share the feedback internally with the relevant team.
torpid vapor
That would be amazing, thank you.