Sync notices — when two phones disagreed

See every time two phones changed the same cost, expiry, service interval or the boat's own numbers while apart — which figure stands, which was overwritten, and who wrote each.

Two people can work the same boat with no signal between them. When the phones meet again the later change stands — always, and never because of who wrote it. That rule is what keeps a boat working offline, and it has one cost: a figure somebody typed can be quietly replaced.

So for the fields where that would matter — money, expiry dates, service intervals, and the boat's own numbers like draft and MMSI — theONE keeps the record. The later value stands, and the one it replaced is written down here with who wrote each and when. Nothing is lost silently.

This is a record, not a repair. The merge already happened. If the figure that stands is wrong, open the record itself and correct it — that correction is then the later write, and it wins. Dismiss on a notice means you have read it; it does not change anything on the boat, and it does not travel to the other phone, because the other captain has his own reading to do.

There is one other kind of notice: a record deleted on one phone and edited on another. The edit came later, so the record is back. That one has no figures — the record itself is the point.

Two things are not a disagreement, and theONE keeps both sides of them. A record made on each phone while they were apart can come in under the same number — two different issues, tasks, observations, systems or trips. Those are two records, not one: both stay, on every phone, and the one made second takes a number of its own. And the boat's survey (engines, generators, tanks and the rest) is settled answer by answer: a phone that renames the boat before it has heard your survey carries an old or empty copy of it, and that copy does not replace your answers. An answer changed on either phone still travels, and the later change stands.

Three more things are kept on both sides. Two work orders made on two phones under the same number stay two, like the records above. A trip this phone made and never sent (one from before the boat was in the cloud) is not replaced by another phone's trip under its number: it takes a number of its own, and both stay — this phone's own copy of a trip the other phone sent is still the same trip. And what pointed at a record by its number — a task's or a bill's trip, a work order's list of issues, a service entry's system — goes with that record to its new number. The rest of the boat's own details are settled the way the survey is, one detail at a time: a phone that changes one of them before it has heard another phone's change (a new MMSI, say, before it has heard she was renamed) carries an old copy of the rest, and that copy does not undo the other change. One thing does not travel this way: a detail emptied on a phone that never sent it filled in.

Steps

1. Open the list

   Account → Sync notices. It shows a count when something needs reading, and "None" when nothing does.

2. Read what happened

   Each line names the record, the field, the value that stands and the value it replaced, why that field is guarded, and which phone wrote each — this one or another. Dates read as dates: a service pushed from November to March says so in words, not as a machine timestamp.

3. Fix it, if it needs fixing

   Open the record and correct the figure. Your correction is the later write, so it stands everywhere once the phones meet.

4. Mark it read

   Swipe a notice left and tap Dismiss. It stays in the list, greyed, so the record of the disagreement is never thrown away.

← All help articles