Nextcloud Deck offline sync recovery,
with plain recovery states.

When your server is unreachable, Deckloud does not block you or throw away edits. Changes (new cards, moves, comments, due dates) go into a local queue on the device, and the app replays them against your Nextcloud server in order once connectivity returns. Reads keep working from the last synced state, so boards stay usable on a plane or a dead-zone commute.

Recovery is only trustworthy if you can tell what is happening in plain words.

• Waiting for network.

  Edits are queued and safe; nothing is lost. The app is waiting for the server to be reachable again.

• Last successful sync.

  A timestamp that answers the real question: how fresh is what I am looking at?

• Retry.

  Replay the queue now instead of waiting for the next automatic attempt, useful right after a VPN reconnects.

• A specific failed action.

  If the server rejects one operation (deleted card, missing permission), that one action is flagged rather than poisoning the whole queue.

Deck's model is card-granular, so most offline sessions replay cleanly: two people editing different cards never conflict. When the server rejects a replayed change, Deckloud surfaces it explicitly so you decide, instead of guessing and overwriting someone's work silently. The server remains the source of truth throughout.

Confirm the server is reachable in Safari on the same connection, then retry the queue. A queue that fails against a reachable server usually has one specific failed action to look at; copy diagnostics from the app captures the sync state (never board content) for a bug report.