Clock Time Entry Record Conflicts

Maybe add a screen shot or send this to support? 

I feel that! We have been seeing more of those this year as well, especially after some of the alert updates.

The best assumption I have been able to come up with (based on a few cases we looked into) is some kind of delayed sync between Aspire Mobile and time entry. For example, if we manually adjust or approve time because it looks like it did not come through, and then it syncs later, it seems to trigger those conflicts.

I have also seen situations where techs had poor reception at clock-out, and it creates multiple or weird time entries that then show up as conflicts after the fact.

Just guessing based on what we have seen on our end, but I would also love to hear if others have figured out a clearer root cause.