Verified Sep 21, 20264 min read

Cloud Sync limits

Review every enforced Cloud Sync capacity, storage, transport, and rate limit.

What happens when a limit is reached

Cloud Sync refuses the affected remote operation and keeps the local scenario and downloaded results unchanged. The Cloud Sync panel names the limit, its configured maximum, and whether waiting can help. It does not report a payload-size or quota refusal as a generic connection problem.

These are Cloud Sync limits, not limits on local editing, solving, saved scenarios, or downloaded results.

Account and workspace limits

Limit	Maximum	What reaching it means
Active cloud workspaces	100 per account	Turn off and delete an existing cloud copy before enabling another one.
Result documents	100 per cloud workspace	Additional result documents cannot be registered in that workspace. Existing local results remain available.
Collaborators and pending invitations	100 per workspace	Revoke a collaborator or cancel an invitation before adding another.
Restricted share links	100 active links per owner	Cancel an unused restricted link before creating another.
Allowed recipients	100 email addresses per restricted link	Create another restricted link for additional recipients.
Concurrent cloud connections	64 per workspace	Close or pause another connected browser and retry.

Document and durability limits

Each result is a separate cloud document. Limits described as “per workspace document” therefore apply independently to the scenario root and to each synchronized result.

Limit	Maximum	What reaching it means
Baseline snapshot	8 MiB	A new cold cloud document or compaction baseline cannot exceed this encoded checkpoint size.
Incremental checkpoint	28 KiB	Larger incremental batches automatically use a full checkpoint, preserving all history, within the baseline and total storage limits.
Candidate storage	32 MiB per workspace document epoch	A document epoch cannot use more candidate bytes than this bound.
Durability checkpoints	1,000 per workspace document per UTC day	Further new checkpoints wait until the next UTC day. Exact retries of an existing request remain replayable.
Exact receipt	3 KiB per row	A durability receipt that cannot fit is refused before a new candidate is written.
Receipt history	2 MiB per workspace document	Further receipt-producing checkpoints are refused when the exact replay ledger is full.
Cloud storage objects	17 per hot workspace document epoch	Hot storage uses 16 candidate slots and one pointer. Cold inactive storage uses one object.
Candidate history tail	14 entries	A full checkpoint after 8 incremental entries keeps normal replay below this storage ceiling, preserving all history.
Active operations	32 per cloud document	Wait for current writes to settle, then retry.
Queued operations	8 per connection	Wait for the current connection’s queued writes to settle, then retry.

Transport and connection limits

Limit	Maximum	What reaching it means
Binary sync frame	8,388,875 bytes	Compressed content is limited to 8 MiB plus framing; decoded content is limited to 32 MiB. Refresh an older browser tab to use the current transport.
JSON sync frame	32 KiB	The individual JSON protocol frame is refused.
Message rate	480 frames per connection per minute	Wait for the rolling one-minute window, then retry.
Data rate	64 MiB per connection per minute	Wait for the rolling one-minute window, then retry.
Pending connection data	16 MiB	A slow or overloaded connection is closed before its unsent queue grows further.
Connection credential lifetime	300 seconds	Active clients renew credentials automatically. A failed renewal asks the browser to reconnect.

Reading a limit error

An explicit limit error follows this form:

Cloud Sync limit reached: Baseline snapshot size — maximum 8 MiB. Reduce the affected cloud data, then retry. Diagnostic: baseline_candidate_bytes.

Rate limits additionally tell you to wait. Capacity and payload limits tell you which bound must be reduced or freed. If GroupMixer shows only a generic connection error for a confirmed limit refusal, report it as a Cloud Sync diagnostics bug and include the displayed diagnostic code.

Troubleshoot scenarios and solvesMatch the reported state to the editor, runtime, result, or storage fix.Scenario EditorEnter the model, rules, preferences, and objective used to generate groups.Understand resultsVerify scores, constraint evidence, pair meetings, assignments, and exports.