We are test driving the DC module with a subset of our people.  We're running it in our QA Lab, since they all have computers at their workstations.  It's not uncommon for them to clock into multiple jobs simultaneously and work on them as a batch.  Sometimes, we are seeing the Evo generated "Time-out" time created when the second job is clocked into is returning a strange time.  I have one employee who was clocked out by Evo at 39:30:00.  I know what the number should be, but DC-G will not accept the correct Time-out.
 
Anyone else encounter this?

Thanks for the prompt reply.  We have "Enable Employee Shift Start/Stop" set to "N".  Would it still look at shifts?

Perfect.  I've set the buffers to match the defined shifts.  Now I can edit the bogus times.
 
Thanks!