Skip to main content
Print

When the office changed the same thing

By the end of this article you’ll know what to do when the sync bar shows a red badge: what the office kept instead of your change, why, and which entries need more than a glance.

Why this screen exists

Two people can touch the same job in the same hour — you in the driveway with no signal, the office at a desk. When your change reaches them and their rules can’t take it, the office’s version wins and your phone falls into line on the next sync. What never happens is that your change vanishes quietly: every refused change is written to Needs review with a reason in plain words, and the bar shows 1 to review in red until you’ve read it.

Open it

  • Tap the red badge on the sync bar, or
  • YouNeeds review. The row only appears once there is something in the history; its line reads All reviewed or 2 to review.

When there’s nothing, the screen says No overridden changes — your work is in sync.

Reading an entry

Under These local changes were replaced by the server’s version. Nothing was lost silently., each entry is one refused change:

  • Job 1042 — which record it was about. A job when the phone can’t name it any more.
  • One sentence saying what happened, from the office’s point of view.
  • Your change: In Progress — what you had set, when it differs from what the office kept.
  • Seen 3 times — the same refusal came back on more than one sync, folded into one entry rather than three.

Tap Dismiss once you’ve read an entry. That takes it off the badge but leaves it in the list; Clear all in the corner empties the list. Neither undoes anything — the office’s version already stands.

The reasons you’ll see most

  • The job moved on without you. Your status change wasn’t applied — the job is already “Completed” on the server.
  • Not yours any more. This job was reassigned, so your change wasn’t applied. Check Work for what’s yours now.
  • Someone got there first. Someone else took this job before your claim reached us.
  • A booking the office couldn’t keep. This job wasn’t created — one of the services or vehicles on it is no longer available. Please create it again. The job disappears from your phone; create it again with what the office offers now.
  • A quote already answered. This quote was already answered before the signature reached us, so the signed acceptance wasn’t recorded. The signature is still saved on this device.
  • A day off the office couldn’t take. That day had already passed by the time your request reached the office, so it wasn’t sent. Request a day that’s still ahead. The request leaves My Schedule; ask again for a day that works.

Money is different

Above the list, in red, there may be a second section: This money never reached the office. Retry it if you can, or tell the office. It’s for a cash or check payment, or an expense, that the office refused to record — $180.00 Cash was not recorded, with when you collected it and why.

Money gets its own section because there is no office version to keep: the cash is in your hand and nobody has a record of it. So these entries survive Clear all, and they offer actions:

  • Retry — shown when the cause can lift. The books are closed for that date. Ask the office to reopen the period, then retry. or You no longer have permission to collect payments. Ask the office to restore it, then retry. Sort it out with the office, tap Retry, and the payment goes on the next sync.
  • Dismiss — always shown. Use it once the office has recorded the payment by hand, or when nothing can be retried — That invoice was voided. Tell the office you collected this. Dismissing means I’ve told them; it doesn’t record the money.

A refused payment also announces itself with its own toast — 1 record was refused by the office — review it.

Good to know

  • Entries are about changes, not about everything the office did. The office editing a job you didn’t touch simply updates your phone; nothing lands here.
  • The list keeps the hundred most recent entries. Refused money isn’t counted against that and isn’t touched by Clear all.

Related

Table of Contents