#salteesam-terminal-timeout
fallow treeBOT
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.
- salteesam-terminal-timeouts, 1 day ago, 28 messages
vagrant ravine
👋 give me a few minutes to take a look
torpid star
thank you!
vagrant ravine
Hmmm... for this one I'm not seeing the terminal being disconnected at all so it's not related to connectivity
torpid star
interesting can you tell what is happening this time?
vagrant ravine
I'm looking but we may have to pull some other folks in to take a look - I'm not seeing anything obvious from the logs yet 😦
I need to head out, but a teammate is around and going to likely pull more folks in to take a look
fallow treeBOT
salteesam
torpid star
okay thank you
main solstice
Have someone looking right now
fallow treeBOT
salteesam-terminal-timeout
torpid star
Thanks!
velvet sun
Hey there, do you have other example payments, or can you share more about how often this is happening?
Are other payments for the same reader successful, or are all failures? For this connected account vs others? Have you been able to try another reader
torpid star
I’ll take a look now
potentially these:
pi_3ONOjgFemSPDAV991M4Bv1jE
pi_3OLVrYFemSPDAV9918EchgQS
pi_3OLVpGFemSPDAV991ajvaqTZ
we have had many reader timeouts accross many different connect accounts. In the past i've opened up threads in this channel and it was mentioned that the readers disconnected before the requests.
but it has been very common and across many different accounts. so it's hard to believe it's all due to network connection. But if in this case you are seeing something different we'd love to know what is going on / if there if anything we can do to fix it
velvet sun
potentially these:
`pi_3ONOjgFemSPDAV991M4Bv1jE`
`pi_3OLVrYFemSPDAV9918EchgQS`
...
The first and third example here appear to have had a single failed request each, then succeeded, while the middle one has had similar repeated failures
And these all appear to be for the same reader
torpid star
yeah
pi_3OLavaIol1CuUBvF0XIq6WeT
pi_3OJmObIol1CuUBvF3lO0V3er
pi_3OJmNbIol1CuUBvF2VOgKYer
pi_3OJmMaIol1CuUBvF33p1OfYF
pi_3OJm8zIol1CuUBvF2tG0jBHk
here are other ones (but these were all determined to be network issues last time
velvet sun
Over the last week, i see ~30 instances of this, all on this reader+account plus 1 other reader/account
Does that align with your observations?
torpid star
yeah it could be? it's been tricky to keep track of but 2-3 accounts in particular have had the most issues
velvet sun
That this is concentrated on a small number or readers/locations does suggest to me a connectivity issue. Have you been able to try another network connection for any of these readers at all, such as a mobile hotspot?
torpid star
we don't have any control over them as they are connect accounts in various locations. but that being said we have been tracking the network connection of our application on a tablet running our app. and they network connection is stable. so its just the reader that's disconnecitng?
and i thought it was mentioned that pi_3ONggpFemSPDAV990J3o2IGa did not have any network issues?
velvet sun
Yea, understood, and the server-driven approach is certainly better for this scenario. It does need to have consistent connectivity, though. Still trying to look into this another way.
Have you tried other readers at these locations?
torpid star
no each location only has 1 reader right now
velvet sun
Right, but sending a different reader and/or a mobile hotspot would be an approach to debugging the issue and isolating the locations network access
torpid star
sure, but these are pretty high cost. it stripe willing to send out another reader for testing?
fallow treeBOT