#perqin_error

1 messages ¡ Page 1 of 1 (latest)

bold zincBOT
open locustBOT
#

Hello! We'll be with you shortly. 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.

  • perqin, 6 days ago, 2 messages
bold zincBOT
#

👋 Welcome to your new thread!

⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime!

🔗 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/1212227756159401994

📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.

⏲️ 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. Thank you for your patience!

somber tiger
#

After getting the SessionExpired error, the reader is disconnected and we start getting another NotConnectedToReader error with message No reader is connected. Connect to a reader before trying again.

thin agate
#

hello! can you share the corresponding serial number of that reader?

somber tiger
#

"readerId":"STRM26229014592","locationId":"tml_FQKoMAmjFGG2jR"

thin agate
#

hmmmm, i'm guessing that you're using bluetooth connectivity?

#

and is that error message you mentioned occurring when you get the SessionExpired error?

somber tiger
#

Yes we are using an M2 reader using bluetooth. And yes, the "Expired API Key provided ..." error message occurred when getting SessionExpired error.

thin agate
#

okay, this is going to require some time to investigate, can you reach out via https://support.stripe.com/contact/email with the reader id, and serial number, with a summary of the issue? We'll follow up on the ticket