Where it usually breaks
And how to keep it from happening.
- A timer is left running overnight.
- A mobile entry is captured on a code that was retired before it synced.
- The same mobile entry is retried and appears twice.
Turn timer events and offline mobile entries into time entries without losing or doubling hours.
Resource starts a timer against a project code from the web, mobile or the API.
Each pause and resume is recorded as an event, and accumulated time is kept on the timer.
Stopping the timer finalizes one time entry with the elapsed time rounded to the policy increment.
On a phone without a signal, Resource records the entry into the sync queue as Pending.
When the phone reconnects, the queued entry becomes a time entry and is marked Synced, or Failed with a reason the person can fix.
And how to keep it from happening.
Start free, then use Proto to change fields, steps and approvals before your team goes live.