07-24-2025 09:21 AM
Does anyone know of a way to filter orders by the device ID that the order was placed on?
I've got a random open/unpaid check from Tuesday on a check that was actually paid and closed on Tuesday. It looks like the ticket populated on a handheld yesterday and items were ordered on the ticket. The audit shows the name of the person who had the ticket on Tuesday, but she did not work yesterday. I can see that the items were added yesterday at 4:01 pm, but I don't have any other orders started at that time. In my mind, if I could see who else put orders in on the same device ID yesterday, I could figure out who created this havoc. But...I can't find 'device ID' as a filter anywhere. For context, we have 30 Toast Go 2 devices and most were in use yesterday.
Needless to say someone will be tasked with clearing caches today... 😏
10-16-2025 11:34 AM
We have a few restaurants with similar device counts, and have also been plagued by this issue in the past. The "ghost checks" (as we had internally dubbed them) appear when a device loses network connection one day, and comes back online the next. If the device had live orders cached on it when it went offline, it will try to push these back up to the server when it comes back online. We've had month-old checks repopulate!
We've partially mitigated this by upgrading our network/wifi infrastructure and relocating the charging stations for the handhelds to a place with better WiFi connectivity. We still get the occasional ghost check, but it has significantly improved. Any time we get one now we put in a support ticket to clear out the impacted check. They can also be voided, as if you look at the order number, it is actually a duplicate/copy of the original- not the original itself repopulating.
In my opinion it would make more sense for a device that has been offline for a prolonged period of time FIRST check for a more recent version of any stored orders first, before just force pushing them up and into to the database.