Skip to content

[No QA] Docs: drop overstated dedup guarantee from SEQUENTIAL_QUEUE.md overview #94037

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
inimaga merged 1 commit into from
Jun 19, 2026
Merged

[No QA] Docs: drop overstated dedup guarantee from SEQUENTIAL_QUEUE.md overview #94037

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion contributingGuides/SEQUENTIAL_QUEUE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

## Overview

The SequentialQueue is how the app keeps its **offline-first promise**: a user can "do their thing" regardless of connectivity, and every change they make is sent to the server **serially, in order, at the right time** (deduplicated server-side on the rare resend from a retry or leadership change), even across going offline, refreshing the tab, or restarting the app.
The SequentialQueue is how the app keeps its **offline-first promise**: a user can "do their thing" regardless of connectivity, and every change they make is sent to the server **serially, in order, at the right time**, even across going offline, refreshing the tab, or restarting the app.

`SequentialQueue` is a **single-flight, first-in-first-out (FIFO), leader-only engine** that drains every `API.write()` request one at a time, with exponential backoff on failure, surviving offline periods and (for most requests) app restarts. It is a coordinator over four collaborators:

Expand Down
Loading