Sync Health — what got dropped, and what got stuck
Find entries the cloud sent that this device could not read, and changes that could not be sent and were set aside, and do something about both.
Two things can go wrong quietly between this device and the cloud, and this page is where both of them show up.
An entry the cloud sent that this device could not read at all. Not one written by a newer version of theONE — those are safe in her record and an update shows them — but one that would not decode. It gets skipped so the entries behind it can still arrive, and it is recorded by its entry number so it can be asked for again.
A change of yours that could not be sent. It is taken out of the send queue and set aside. That matters more than it sounds: before, a change the server would never accept sat at the front of the queue re-trying every thirty seconds, and nothing behind it ever went up. Setting it aside is what lets everything else through. Nothing is deleted — the change is still in her record on this device, and you can put it back. The list is kept on the device beside her record, so closing the app or restarting the phone does not lose it.
A change that simply got no answer — a timeout, a server error, a marina sign-in page in the way — has not been refused, and it is not set aside straight away. theONE tries it again by itself while theONE is open: after 15 seconds, then waiting twice as long each time, up to 5 minutes between tries, and never sooner than the cloud asked. It is set aside only after ten failed tries, counted no more than once a minute, and only once a change behind it has gone up — proof the link works and that one change is the trouble. On a link that fails for everything, nothing is set aside: the queue waits and keeps trying.
When neither has happened the page says so. "Nothing has been dropped or set aside" is a result, not an empty screen.
Steps
-
Open it
Menu (☰) → Settings → Sync Health. The row itself turns red and says what is wrong, so you do not have to go looking. With nothing wrong it reads "Nothing waiting, nothing dropped" or how many changes are waiting to go up — and on a phone that is not signed in, "Kept on this phone · sign in to sync": with no session nothing goes up, so it counts nothing as waiting. The page's Queue says the same, Waiting to go up: None.
-
Ask the cloud again
For entries that could not be read, this re-reads everything from just before the earliest one. Entries already on this device are recognised and cost nothing. If they come back unreadable a second time, the problem is at the other end — send the entry numbers on this page to support.
-
Put changes back in the queue
For changes that were set aside: sign in again, or wait until whatever refused them is fixed, then put them back. Each set-aside change is headed by what it was, in plain words — Crew book card update, say — with the reason under it; one set aside after many failed tries says that every try failed and nothing is lost. They go to the front of the queue with a clean slate, and theONE sends them straight away. If they are refused again they come straight back here.
-
Files the cloud refused
A photo, receipt, scan or manual the cloud refuses for itself — too large, or not your role's to hold — is set aside here too, named, with the cloud's own words. Put them back in the queue sends it again. A file whose refusal is about your sign-in or your access to the boat is not set aside: it waits in its queue until that is sorted. The Set aside number under Queue counts changes; files are listed above it. A file over the 25 MB the cloud takes is set aside here as soon as it is added, with that reason, and stays on the device it was added on — on another device its document shows it as Over 25 MB, with nothing to download. A file the cloud keeps failing to take is set aside here after eight tries, with the cloud's answer — and the files behind it go up meanwhile.
-
Queue paused is not the same thing
If the page says the queue is paused because you are signed out, no longer have access to this vessel, or the cloud does not accept this device's id, nothing has been set aside. Every change is still queued and goes up as soon as that is sorted — the problem is the account or the device, not the changes. The same holds when the boat was marked sold: the queue stops with the cloud's words, and nothing is set aside.