We are experiencing an interesting error on our scanners and wanted to see if anyone else had observed the same issue.
Our ticket takers report that intermittently, a ticket will show up as "Ticket Already Recorded" even though the guest is entering for the first time. It will happen to one ticket out of an order, while all the other tickets scan just fine.
I had a chance to see this myself today. I was scanning tickets for a family of four. One ticket out of the bunch showed "Ticket Already Recorded" while the other three scanned successfully. I kept the stubs and looked at the order in the client. In Order History, the three tickets showed as attended, while the one that threw the error did not.
After looking in Tessitura, I tried again to scan the ticket, and it scanned just fine. That was about 10-15 minutes after the first scan attempt.
This has happened with multiple scanners. We are using Motorola MC40.
Anyone else run into this?
Thanks!Jennifer
Hi Jennifer,
Do you have access to the database tables? All scans are logged in the table [T_NSCAN_EVENT_CONTROL]. It would be interesting to see if the "ticket already recorded" was logged in there. Might also be worth seeing if any of the other tickets in that order had been recorded as being scanned twice.
We had an issue of ushers accidentally double scanning a ticket, if the scan button is pressed twice in quick succession, the request gets sent twice. The "ticket already recorded" message would follow so quickly after the OK one, that on the device it just looked the ticket had already been scanned. Not quite the same issue as yours, as ticket would show up as attended, but perhaps it's a delayed response from a previous double scan?
Phil