Almost everything a yacht sends up is applied by the cloud without anyone noticing. The Sync errors section of Vessel Settings → On-board app is where the exceptions land.
When there is nothing to see, it reads No unapplied events. Vessel sync is healthy. That is the normal state.
The list
Each row is one change the yacht sent that the cloud has not applied. The newest are first, and up to the 50 most recent are shown. The columns are:
- Received: when the cloud got it.
- Event: what kind of change it was.
- Aggregate: which record it belongs to, with its position (seq) in that record's history.
- Status: either the error explaining why it could not be applied, or Pending — not yet applied for a change that has arrived but not been processed yet. Pending rows normally clear on their own. One that lingers may be waiting behind a stuck change to the same record.
View payload on a row shows the raw contents of the change, and Hide payload collapses it. That detail is for Nauticare support. The error message is usually enough to identify what is stuck.
The list covers changes the yacht sent up. Two other kinds of problem show on the sync pills rather than in this table: files that failed to upload, and cloud updates the yacht could not apply.
What crew see
The same problem shows aboard as a red sync pill reading, for example, 2 changes couldn't sync — contact your admin. In the cloud app it shows as 2 changes from vessel need admin attention on the yacht's pages. Neither side hides it, because a change the cloud never applied is work that exists only on the yacht.
Replaying failed changes
Stuck changes do not clear themselves. Each one is retried for a while and then set aside, and anything later for the same record waits behind it.
When failed changes are present in the Sync errors list, Replay failed changes appears above the table. Clicking it re-runs every failed change chain for the yacht's active device and reports how many changes were replayed and whether any records are still failing. Once a replayed change succeeds in the cloud, the on-board app picks up the confirmation automatically and clears its warning (and re-queues any file uploads that were waiting on that record). If a record still fails after replay, Nauticare support needs to investigate the underlying cause.
Stuck changes also matter for decommissioning. A yacht cannot finish a decommission while changes are still stuck, because completing it would throw them away. Clear them first, or, if the data really cannot be recovered, accept the loss deliberately. See Long Outages and Hardware Failure.