Time entries showing incorrect durations

An auto-captured time entry in the Servinix Go app shows a duration that is longer or shorter than the actual time worked.

Why this happens

A break was started but not ended, leaving a job entry running through break time and inflating its duration.
The shift was ended while a job was still active, causing the job entry to close at the same time as the shift.
A job-start or job-end event was queued offline and replayed at the wrong time, shifting the recorded timestamps.
The tech left a job screen without tapping the complete or pause action, so the auto-close fired at an unexpected time.

In the Servinix Go app, tap Time entries (from the job detail or the Me tab).
Tap the incorrect entry to open the edit sheet.
Adjust the Start and End times to reflect actual times worked. Both fields use 24-hour HH:MM format.
If the entry was auto-captured, the app requires a Reason for edit before saving — add a short note such as “Forgot to clock out on arrival”.
Tap Save changes. The duration recalculates automatically.
If a break entry is missing entirely, tap Add entry, select type Break, enter the correct times, and save.

Entry type cannot be changed on an existing entry. If the type is wrong, delete it and add a new one with the correct type and times.
Shift and break entries are always non-billable. If a job was recorded as a shift, delete it and add a Job entry with the billable toggle on.
If entries are consistently wrong, verify location and motion permissions are set to Always in device settings. The app relies on these to fire lifecycle events accurately. See grant-location-and-motion-permissions.
Contact Servinix support if timestamps fall outside the actual shift window. Provide the job ID, device model, and incorrect entry timestamps.