#bwurtz999 - 15 minute Terminal issue

1 messages · Page 1 of 1 (latest)

wanton trout
#

Thank you for the heads up. I will check in to if this was part of something bigger. Otherwise, would you be able to upload logs and whatnot to our support site if you want us to look further in to this?

#

If you are just reporting to report, that is cool too.

copper drift
#

I would happily upload something but I'm not sure what I would upload. The JS library wasn't throwing any errors, it just couldn't find the reader

#

Specifically, what could I upload that would help?

wanton trout
#

Figuring out what if anything you can send us now. You may be right that there isn't anything to upload from your side

copper drift
#

Got it. Thanks

#

Yeah I realized it wasn't much to go on for you guys but I also felt like I should tell someone

#

It's one of the P400 Verifone models if that matters

#

Might be unrelated, but I've had issues with those in the past not picking up wifi networks. The screen would show 'No available Wifi Networks' when I knew there were wifi networks available

#

Potentially not related at all, but I thought it was worth sharing

wanton trout
#

Do you have multiple locations for these terminals? If so, was this just at one location or all of them?

blazing lodge
#

@copper drift You still there? We're curious about the location question above. 🙂

copper drift
#

Hello sorry

#

Yes I'm here

#

@blazing lodge

#

It was only at one location

#

tml_EjlB0AQAXPineF

blazing lodge
#

But you have other locations that did not experience this issue?

copper drift
#

yes

#

I think 6 others that did not report an issue

#

I recently switched this location to direct charges, if that matters

#

All the others are still on destination charges

blazing lodge
#

That shouldn't matter when it comes to discovering readers, unless you were maybe discovering readers on the wrong account? But if that was the case I don't think it would have resolved itself. Sounds more like an intermittent network issue perhaps?

copper drift
#

Possibly, but the network there is generally very strong

#

But that could be a possibility

#

But both devices (the iPad and the reader) both said they were connected to the same network

blazing lodge
#

Could there have been a temporary issue on the server providing the connection tokens to the iOS app that was then corrected?

copper drift
#

hmm I don't think so... I didn't make any changes to the code this morning. And I don't have any errors showing in my reporting system

#

And all my other locations were fine

#

It was working throughout the morning for breakfast service and then around 12:30 the issue started appearing

blazing lodge
#

Hm. Could the Terminal readers have been registered with another location/account and then registered back?

copper drift
#

although every time I've had an issue it's always been on my end and never with Stripe

#

No the reader has been at that location for a while. I converted it to direct charges last week

#

Ran fine all last week after converting it. It had been running destination charges for a few months before that, again without issue

blazing lodge
#

Hm. Only thing I can think of to suggest is to add additional logging for things like which platform account is being used, which connected account, etc. and if it happens again see if the logs reveal anything.

copper drift
#

Yeah hindsight is always 20/20. I'm kicking myself because I don't have logging info for connections when there is no error thrown. I should add that

#

Hopefully it was just a wifi issue that sorted itself out. I really appreciate the follow through from you guys though. The support here is always great and I really appreciate it