platform-guideline checked
Workbox Background Sync
Documents queueing failed requests, replaying them when future sync events fire, browser-managed retry intervals, fallback replay behavior, and retention limits for queued background work.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Offline mobile retry | Choose offline mobile retry when a mobile action should be preserved and retried after connection loss, flaky network, app backgrounding, or policy-limited connectivity. | The UI never reports server success for a mobile action that is only saved locally or queued. | Supports queued failed requests, later replay, retry timing, fallback replay, and retention limits. |
| Sync state | Choose sync state when local and remote copies both matter and their reconciliation status affects trust, next action, or data integrity. | The sync surface never upgrades local saved or queued work to synced until the remote system confirms acceptance. | Workbox supports queued failed requests, sync-event replay, browser-managed retry timing, and retention limits. |
Evidence Role
This source is treated as platform-guideline evidence. Use it to validate the decision rules above, not as a visual style reference.
Publisher: Chrome for Developers. Last checked: .