#sarthak17_docs
acoustic owlBOT
👋 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/1309020661515030559
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
stray arch
hello! Those information can't be found via the Dashboard. You can see some information about the device here : https://dashboard.stripe.com/test/terminal/readers/tmr_xxx
stray arch
it's up to you to log the relevant information for all of those details into your own DB
for example, when you handle unexpected disconnects : https://docs.stripe.com/terminal/payments/connect-reader?terminal-sdk-platform=js&reader-type=internet#handling-disconnects, log that the terminal disconnected to your own DB
velvet linden
Do you have anything on this because today one my customer have 3 payments inside 5 min but during the 2nd payment we got the information that terminal is gets disconnected but for 3rd transaction it gets connected automtically so thats why I need logs of terminal what was happening during that.
stray arch
I understand, but unfortunately, we don’t have any information about connection and disconnection attempts available via the Dashboard. To debug this, you need to add your own logs to help identify what might be happening during the transaction process.