Time clock problems are increasing

Casey Z. shared this problem 4 hours ago
Pending

We are very close to abandoning the IO time clock. Is there anything that can be done to get it working more consistently? All of my employees have problems, whether they are using the app or the browser. I just did a quick test on my app and here's what happened: I hit the "clock in" or "clock out" button and nothing would happen on the first one or two attempts, then the options disappear. I open the time clock again and it says "Failed, please try again". I click some more times until it eventually looks like it worked. Then I go into payroll and I see this:

202686895ac3c90230cfdaffd70befeb


Here is a video from my phone. It didn't record audio, but if you look closely at the "clock in" and "clock out" button you can see it flash each time I hit it. https://photos.app.goo.gl/cwPHb4Y5X89oYRpg7

This certainly isn't the only problem, but it's what happened on my first attempt.

If there is nothing that can be done to improve this feature, please let me know soon so we can find a suitable alternative.

Comments (1)

photo
1

I have a developer taking a look at that video...just in case they ask...what worker username are you logged in with in the video?

photo
1

caseyzegar

But this type of thing is happening to everybody. There are so many problems, and it involves so many people, I don't know how anyone will figure it out. I don't have any way to record what each employee is doing every time they make a punch.

photo
1

We have identified the issue in the video, clicking the clock out button multiple times causes the multiple entries in payroll (with no matching clock in). The issue is related to the timeclock needing a GPS coordinates that are logged on the time clock. This can take up to 30 seconds for the phones GPS to get an accurate location. At a minimum, the buttons will be disabled to prevent multiple clock in / clock out events that were sent erroneously. We will also investigate other ways to improve the user experience. The 'failed, please try again' error displays when these multiple records are being processed out of order. IE: each clock in needs exactly one clock out. If there are two clock ins, or two clock outs, this will show.

photo
1

After further investigation into the issue presented in the video, we can see this was caused by invalid time clock records that were created in June 2025. These are records that had an invalid clock in time, and were updated (in the video) with a valid clock out time. Having an invalid clock in time caused the issue you are seeing on payroll for 4/29. We prevented these invalid records from being created back in September, but the invalid entries were not removed. We will be removing these invalid time clock entries which can cause the issue you have presented. Do you have any other payroll examples?

photo
1

Cool, thank you.

Username: brianjohnson

9224f9511097f233786f6a0236dd7fe0

photo
Leave a Comment
 
Attach a file
You can't vote. Please authorize!