01 /Tag — Offline Sync
13 articles in this topic.
Cancel queued mobile work through explicit pre-send, in-flight, and completed states with race handling, dependent-operation rules, and truthful customer feedback.
Recover expired authentication during offline sync with preserved operation ownership, bounded refresh, current permission checks, and clear states for sign-in or manual review.
Handle offline ordering with separate display time, causal dependencies, server revisions, and deterministic tie-breaks instead of trusting device clocks to establish business order.
Handle two-device offline conflicts with base revisions, field ownership, explicit merge rules, preserved user drafts, and tests that change arrival order.
Handle partial mobile sync batches with per-operation outcomes, explicit atomicity rules, safe subset retries, and customer summaries that preserve unresolved work.
Keep offline deletion consistent with durable removal markers, explicit conflict policy, retention-aware propagation, and tests for stale devices returning after long gaps.
Keep offline actions bound to their originating account and workspace through durable ownership, fresh authorisation, account-scoped storage, and explicit recovery after sign-in changes.
Measure mobile sync through separate local-save, attempt, server-acceptance, attachment, and recipient milestones so delivery claims reflect established outcomes.
Preserve offline operation order through explicit dependencies, per-resource sequencing, server revisions, and tests that allow independent work without breaking business invariants.
Prevent duplicate offline effects with stable operation identity, server-side deduplication semantics, atomic processing, and tests around lost acknowledgements and concurrent retries.
Show mobile sync states that distinguish local durability, queued work, server acceptance, attachment completion, and manual review without implying delivery too early.
Show offline changes needing review with task-level explanations, preserved drafts, current server context, and explicit resolution actions that remain valid under concurrent edits.
Sync Flutter work after long disconnection with durable operation records, fresh access checks, bounded recovery, conflict handling, and truthful local-versus-server status.