#salteesam-terminal-sdi-busy

1 messages ยท Page 1 of 1 (latest)

crystal fableBOT
dim tangle
#

Hello! Has this started happening recently, or has this been going on for a while?

remote cradle
#

We've seen it with multiple different readers using different wifis (in different locations) for the past few months

dim tangle
#

Gotcha - do you have an example reader serial number ID + timerange for when this error is occuring that I can look at?

remote cradle
#

i have seen it on our test reader as well let me just find that info

#

serial number WSC513142024289
terminal id: tmr_FUHnNQ66j4jdPy

#

i don't have an exact time frame but i've seen it today or yesterday if i'm remembering correctly

#

the connect account it is associated to is tmr_FUHnNQ66j4jdPy if that is helpful as well

dim tangle
#

If you don't have a time frame do you have a specific intent ID / request you know that was timing out?

remote cradle
#

i found one here pi_3OK2bPIXJEsTqc6v2XmiJH5k

dim tangle
#

๐Ÿ‘ give me a few minutes to take a look

#

salteesam-terminal-sdi-busy

dim tangle
#

Just a quick update - I'm still looking, it at least doesn't seem to be integration related and my guess is that it's connectivity related, but still reading through logs

remote cradle
#

okay thank you for looking into this!

dim tangle
#

Okay found the log - yeah it looks like the reader got disconnected a couple minutes before the request to process pi_3OK2bPIXJEsTqc6v2XmiJH5k went out - so I think in this case it was just bad lluck

remote cradle
#

Is it pretty common for the reader to disconnect throughout the day? i can assume in some cases it's low quality wifi, but because we've seen it happen in multiple locations it's difficult to believe that's the only issue

dim tangle
#

It's common to see random disconnections happen, but it's also tricky to narrow down which ones are because of bad wifi vs which ones are because of something else

remote cradle
#

okay what are the other issues that could be coming into play here?

dim tangle
#

It really could be anything - it could be the reader is busy with an update, maybe it's completely offline, or maybe it's busy with another request

#

Those would have slightly different error messages, but again, there's a lot of variety in what it could be and it's hard to know without concrete examples

remote cradle
#

okay if it continues i'll come back with more PI examples

dim tangle
#

๐Ÿ‘