#hendie_error
hearty nebulaBOT
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.
- hendie_api, 23 hours ago, 44 messages
- hendie_webhooks, 1 day ago, 33 messages
compact hornetBOT
đ 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/1235309741476024393
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
drowsy stream
Hello
sinful phoenix
hi
drowsy stream
Taking a look
sinful phoenix
np
maybe the error happened just in the regular interaction with the customer. I now notice on the PI page that the transaction actually eventually completed, so I assume the lack of pin was actually addressed by your flow. I guess I was just a little alarmed when I saw that error in our logs.