Hello ​@jgrasch- Time entry conflict can be caused by my multiple reasons, including different end times. The conflict alert is asking the user to choose the correct one, and the incorrect one will be thrown out. This can happen if the mobile user was in offline mode and stopped time, and then stopped time again later when they're connected again, and then later that offline time was uploaded and creates the conflict.

If the time was recorded on the default device while in offline mode--and then time was updated again on another device--when one comes back online it can cause double entries and conflicts.

If you want to know which line is correct I recommend to talk to the crew/employee, or maybe look at other jobs that day and see if time on another job was started before the latest end time, etc.

There is a KB Article in the works regarding this.  In the meantime, this document may help. 

Thanks ​@rc3, this appears to clear up a lot of what we were wondering.