NOT Urgent. Enjoy the holidays and look at this later

Can you please promise Casey, that you'll at least enjoy the holidays.

Thank you

I have fixed some faulty time clock entries for that worker, it should now allow them to clock in and out.

I looked at the issue with Brian Johnson, and I noticed the last time clock entry did not have a date for the clock in. I'm not sure if there was supposed to be one, but since it was missing - it didn't calculate the time properly. I set the clock in time to the same as the clock out time (effectively 0 time) and it appears to have fixed the issue for that worker on 1/8. Perhaps there is a similar issue with the other examples that can be fixed in the same way? Let us know if you need further assistance.

This morning, each of these employees has an additional punch that was not there yesterday. Is this something that you guys are working on, or can I delete that punch and see what happens?

I'm not aware of us making any changes, are you able to find out how these entries were added?

It looks like someone on your end is working on it because there is another new punch, I see what they are trying to do, and it appears to be clearing up the problem.

Update: I see your other comment now, so I understand that you added the clock in time. That looks like it will clear up this problem. I'll let you know if this continues to happen.

If we can figure out how these improperly created time clock entries are being added, we can try to prevent them from occurring in the future. Are these being added on the payroll report, worker app?

We will recreate the process and make a video for you.

I have some more info, but no video at this time. At least some of these problems happen like this example:

Employee punches in for shift. Employee forgets to punch out at end of shift. Manager adds the punch out time. This does not register on the employee side, so the employee time clock still thinks they are punched in. Employee punches out at the beginning of their next shift (this is the punch that causes the problems), then immediately punches in. The punch out at the start of the shift creates a shift with no start date/time.

I think the solution is for the employee time clock to change status when the manager addds the out punch. Does that make sense?

Ok, so you think its that if the manager fixes timesheet for worker we need to be sure that the worker can see this update too?

Workers can't see punches, so I don't think that's the correct way to describe it. Their timeclock generally knows whether they are punched in or out. If they punch in in the morning, the next time they open the timeclock, their only option is to punch out. The only time this is not the case is when a manager has added a punch. If the worker punches in, then the manager punches them out, the next time they open the timeclock, their only option is to punch out, even though they are already out.

Does that make sense?

Got it yes. So then they end up with a second "clock out" because they have no idea that the manager has already updated. I am letting a developer know now

Is the worker not seeing that a manager clocked them out from the app, website, or both?

From what I understand, they are all using the workers site, not the app. We can test it today with the app.

Here is a little bit more info about what is happening

https://www.awesomescreenshot.com/video/36701325?key=dee4a2031b3c714d7bb3ee7e23ffda4d

I've tried to reproduce the issue and have been unable. Can you provide a recent example of the time clock issue? Also a way to reproduce the issue? I tried clocking in and out, not clocking out, changing the time. You mentioned deleting a time clock entry, what did you mean by this? I'm assuming this issue is occurring due to the time clock or payroll being used in an unexpected way. We have not had any time clock issues reported by other users, and there have been no changes to the code. We did have a server update in December, which could have caused a change in the way it was working before.

Also, with this error

The page content was out of date.  Please try again.

you would generally refresh the page to fix this issue. If this doesn't resolve the issue, let us know when and with what worker it is happening and we can figure out what is causing that specific issue.

Thanks for the update. I almost sent you an update last week as I learned more about how this problem happens. Basically, when there was an incorrect punch, my time clock guy would delete the punch in payroll, causing a series of issues. While testing different scenarios, I found that we could get around it by adding a punch at the same time as the incorrect punch, rather than deleting the incorrect punch. That then shows a punch in and out totaling zero minutes. I shared that info with Chad Burkholder and he said that's how he handles incorrect punches; that's why he doesn't see the same problem we were having. I think we are good now with this process.