#ninjamasta_api
queen troutBOT
👋 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/1351976394262974494
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
worldly bronze
The associated payment intent -> pi_3R46C5F0x5SNp72D0SfayLrA
As far as I can tell this is related to networking issues? We have checked the battery on the reader and it is charged. Can you see anything on your end or have any reccomendations to fix it? The retry logic works sometimes, but takes a while and doesn't always work.
dreamy axle
Hi, it is possible to get this error and we document this here: https://docs.stripe.com/terminal/payments/collect-card-payment?terminal-sdk-platform=server-driven#reader-timeout
What is the Serial Number of the reader and what specific timeframe did you see this error?
worldly bronze
When the issue occurs, it usually starts with a terminal_reader_timeout "Reader is un-reachable" error followed by a series of terminal_reader_busy "Reader is busy" errors. Let me get the timestamps.
The issue occurred yesterday at Mar 18, 2025, 7:52:57.441 PM (UTC Time)
Let me track down the reader serial number....
I believe this is the reader: tmr_E8N2Ug0JstHENp (Serial: WSC513142044188)
dreamy axle
From looking at this on our end, I see that you disconnected the reader multiple times after wards but I do not see any issues prior. Still looking
worldly bronze
Ok, thanks for looking. We also got similar errors at the following timestamps, but the retry logic eventually worked on these, after 3 or 4 retries:
Mar 18, 2025, 8:50:25.611 PM
Mar 18, 2025, 8:59:22.654 PM
Mar 18, 2025, 9:03:11.566 PM
Mar 18, 2025, 9:45:20.458 PM
All UTC times
The reset of the day, most transactions worked without issues, maybe one retry on a few for a busy error.
dreamy axle
Are you sure that is the right reader? I do not see any issues on my end for the above timelines on that reader
worldly bronze
It could be this one also, we usually only use 2 readers: tmr_FR5YMAGkksQ3es
We also use a third reader, but not very often: tmr_Ezeo9ACuEurVhz
dreamy axle
For the above issue, which reader did you use?
Yeah, it is for that reader you shared earlier.
Let me confirm with a teammate if they see anything of suspect
worldly bronze
Owner says most all the issues occur on Cape Coral Register 1, which is tmr_E8N2Ug0JstHENp ... trying to look through server logs to confirm reader id...but I think that is it.
queen troutBOT
worldly bronze
Ok, yes, I can confirm that the first timestamp/issue listed would have been on reader tmr_E8N2Ug0JstHENp.
bright venture
Hello, no updates at the moment but I am looking into this with a colleague, am not immediately seeing anything that indicates what was blocking these calls. Will let you know what we find
worldly bronze
Ok, thanks.
bright venture
As best we can tell these issues may be because of transient network issues on your local network, even for the reader busy errors. Do you have another network that you can connect the reader to to test to see if it still sees the same amount of these errors?
worldly bronze
Checking....