#bwurtz999

1 messages ยท Page 1 of 1 (latest)

cold drumBOT
mild niche
#

Hi there

#

Give me a moment to take a look

summer loom
#

Thank you

mild niche
#

So far nothing jumping out to me.

#

Still looking though

#

Hmm yeah on my end it just looks like the card was never presented.

#

Let me see if I can see any other logs internally

summer loom
#

Interesting. I wasn't onsite but I trust the report I got from my manager. She says the card was tapped and then the reader screen reset

#

Still nothing to indicate that a card was presented?

mild niche
#

Not seeing anything no. Is it possible there was a network blip on your side during this time and the Reader lost conection?

#

Like that is the only thing I'm coming up with

summer loom
#

Hmm ok. I guess that's possible

mild niche
#

Is it possible that there is a mixup in PI? Like there was another PI handled by that reader successfully ~15 seconds beforehand

#

Or is it more likely that was just another customer?

#

Not sure how long your checkout process takes

#

But could that second PI have been created on accident and just got mixed up with the first one when looking at it?

summer loom
#

I could investigate that. This is used at roughly two dozen locations so if it was prone to that kind of error I feel like it would be happening much more freuqently

#

But I can check

#

Something else has come up just now that I think is more urgent. Can we switch to discussing a different error?

mild niche
#

Sure

summer loom
#

Thanks!

#

So I have attempts to instruct the card reader to accept payment that are failing

#

And they are happening right after I update a payment intent

#

Here are three successive request IDs

#
  1. req_wxnWansKJN53tv
  2. req_QcZ38v2FuD5xtb
#
  1. req_pPa9sCQOurPIi8
#

1 succeeds and 2 and 3 fail

mild niche
#

Yeah that looks like essentially an object lock to me. Surprised we don't respond with a 429 here...

summer loom
#

Any idea why they would be failing?

#

The update payment intent function has finished before the accept payment function is called (in my code)

#

But it says the reader is busy

mild niche
#

Ah okay these are sequential

#

So you get the response

#

Hmmm

#

That's strange

#

Let me look more

summer loom
#

What I've done as a quick fix is to put in a loop that runs 10 times and tries to trigger the reader to accept payment each time if the previous one failed

#

Hopefully that works

#

I don't experience this error locally

#

So it's tough to debug

mild niche
#

I'm working on tracking down what request the reader is hung up on

summer loom
#

Thanks

#

Yeah that's what's so confusing for me. I don't know what else it would be doing

mild niche
#

Yeah I agree. Give me a few more mins

summer loom
#

Thank you

#

I'm hearing from several managers about this problem. This is affecting multiple units. Seems to have started happening in the last day or two

mild niche
#

Got it. A colleague is looking with me as well. If needed we will escalate to our Terminal Eng team as this doesn't seem expected afaict

summer loom
#

The loop I put in isn't working either

#

It waits 30ms before retrying and each time it fails

#

Something strange I just noticed is that sometimes it is returning a busy error and sometimes is it returning a unreachable error

mild niche
#

Yeah we are seeing some network errors for the reader

#

Which aligns with that

summer loom
#

Some use a wired connection and some use wifi

#

if that matters

#

Is there anything I can do right now to try and fix this?

mild niche
#

Still checking what we can see from our end. I think there is a chance you are going to want to check on network connection and see if that is related here. I'd like to confirm from our end though that it is network related as the root cause

summer loom
#

I understand that's a possibility, but I'm having this issue with at least 3 different locations all with different networks

#

Is the 'run health check' in settings the right way to check the connection?

mild niche
#

Yeah would be curious what that shows

#

Going to get someone from our Terminal Eng team to see if they have further insight here. Will likely take a few mins to get their eyes on this so hang tight

summer loom
#

OK thank you

mild niche
#

To clarify, you are only seeing this if you update a PI ahead of attempting to process?

#

And it works if you don't call this update?

#

Or is that not necessarily true?

summer loom
#

I think it can happen in different scenarios but the main one I'm focused on right now is when I update the PI and then immediately (attempt to) make the reader ready to accept payment

mild niche
#

Gotcha thanks

summer loom
#

Any update here?

mild niche
#

Not yet. Still waiting on someone from our Terminal team to be available.

summer loom
#

ok

mild niche
#

Okay someone is looking now. Couple more mins

summer loom
#

Thank you!

cold drumBOT
cold drumBOT
obsidian mist
#

Sorry for the lack of updates- we've still got folks looking, it's just taking a while

summer loom
#

thanks @obsidian mist

#

After some more testing with my manager, I think the unit is defective

#

It's plugged in and charging but it's losing charge

#

I had her restart it and the problem continued

#

I ran a health check on the network and it said it was fine

obsidian mist
#

Is this just happenign for the one unit, or multiple?

summer loom
#

But then the request to update the reader failed again

#

One

#

Turns out the issues at other units were different problems

obsidian mist
#

gotcha

#

Just to confirm - the reader that has issues is STR706250005014 right?

#

or is it a different one?

#

@summer loom Just checking to see if you saw my quesiton

cold drumBOT
summer loom
#

Sorry I got distracted

#

I believe the faulty reader is WSC513128025990

obsidian mist
#

๐Ÿ‘ thank you!

summer loom
#

Sorry for the delay

#

Does it sound like the reader is faulty to you?

#

Could we get a replacement?

obsidian mist
#

still checking some things but can you quickly confirm - after the reboot are you still getting the same errors you saw before? From the logs we have on our end it does look like some requests are succeeding

summer loom
#

Yes even after the reset we were not able to set the reader display, even after validating the network using 'Run Health Check'

#

I don't see any successful requests to tmr_FA2f6w0fdvvYel

#

Can you point to a successful request for that reader?

#

And even if we could connect to it successfully, the battery was losing charge

#

While plugged in

obsidian mist
summer loom
#

Hmmm

#

that's a clear reader screen request right?

#

This was after the reboot

#

But right before this we were getting responses like for req_zIucp2nohj8r4g

#

Same exact action

#

Weird

obsidian mist
#

Is it possible for you to try (the set reader display) one more time right now and see what happens? I wonder if it just took some time for the reader to correct itself after the reboot

summer loom
#

Tyring now

#

And now it's working

#

This is driving me insane

obsidian mist
#

phewww I was worried for a minute there you were seeing something completely different

summer loom
#

No I see it working

#

But right after the reboot it definitely wasn't

#

What would cause that?

#

And does this mean the battery issue is fixed too?

#

The manager is gone for the day so no one is there to check it. Can that be viewed over the API?

obsidian mist
#

Yeah I'm asking now on what the issue actually was - my guess is that whatever it was took some time to fully resolve itself after the reboot

#

It's hard to say for sure whether this fixed the battery issue and with the server-driven integration there's no way to retrieve the battery levels through the API either

summer loom
#

Any initial ideas about the unreachable error? Today was day 1 for a new client and right now I've got nothing to tell them...

obsidian mist
#

Nothing on that yet, but for the battery one - while you can't retrieve that through the API I definitely see from our own logs that the battery levels for that reader is steadily decreasing

summer loom
#

Dang

#

My manager tells me it's plugged in

#

The charging symbol is visible

#

This photo is from a few hours ago

#

This photo is from a few hours ago

obsidian mist
#

Yeah I'd say the reader should just be replaced at this point - you should be able to start that process through the dashboard now

summer loom
#

Ok where do I do that in the dashboard?

obsidian mist
#

The options that are available will depend on how recently the order was made

summer loom
#

Great thank you very much!

obsidian mist
#

๐Ÿ‘ glad we could help! (and sorry that this device wasn't working as expected).

summer loom
#

All good