Time clock problems are increasing

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.

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.

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?

Cool, thank you.

Username: brianjohnson

On April 28, 2026, worker Chris Branch cleared the clock-out/break-out times on four old Brian Johnson timeclock rows. Those rows then stayed open until they were later closed around April 29, so the payroll page treated them as long unassigned punches ending inside the selected payroll day. Could we find out why this was done? Was Chris trying to edit these times? If this is a common practice then clock out times are getting removed and then the next shifts clock in time is going to be skewed as well.

This seems to stem from an incident in early April where a bunch of shifts disappeared from our system, then someone on your end restored them. We will have to keep that in mind going forward, but this may be the end of that problem. Is there any way you can give us access to a log, a report to show open shifts, or any other tools that could help us find and prevent these problems?

The other problems we regularly have - where our employees report that they can't clock in or can't clock out - those are impossible for us to determine the cause without access to more information. I can try to send you guys a message each time it happens, if you like.

Thank you for investigating this.

We made some fixes. Contact us if you still experience issues. Thanks!

I still have this mess on Brian Johnson's payroll. I don't know how to clean it up. This was all caused by the tome when a bunch of shifts disappeared, then you guys restored them. Here is the ticket from that issue

https://rental.software/support/topic/1239131-shifts-disappeared-from-new-delivery-planner

We are looking at it!

Those are fixed by restoring original values. We found that CBranch manually cleared the end of those shifts on the payroll report causing the issue. Our changes should prevent this in the future. Let us know if you find more.

April 10th again, so I'm sure it was caused by the same set of circumstances. I don't know how to fix it though. Hopefully this is the last one of these. I do have one more issue, which I will put in a separate comment.

Looks like the first was listed as a break. The second was a clock in/out. Are the hours totaling correctly? Is this one you need us to fix as separate shift clock in/outs instead of a break?

It's not totaling correctly. It should be 5.88 hours on the 27th and 6.22 on the 28th. The 6.22 hours is being counted twice. It's on the 28th, and it is included in the 12.10 hours on the 27th.

Does that make sense?

Thank you. It looks good now.