GroupMixer
Browse Help topics
Back to Help
Verified Sep 2, 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

LimitMaximumWhat reaching it means
Active cloud workspaces20 per accountTurn off and delete an existing cloud copy before enabling another one.
Result documents100 per cloud workspaceAdditional result documents cannot be registered in that workspace. Existing local results remain available.
Collaborators and pending invitations100 per workspaceRevoke a collaborator or cancel an invitation before adding another.
Restricted share links100 active links per ownerCancel an unused restricted link before creating another.
Allowed recipients100 email addresses per restricted linkCreate another restricted link for additional recipients.
Concurrent cloud connections64 per workspaceClose 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.

LimitMaximumWhat reaching it means
Baseline snapshot512 KiBA new cold cloud document or compaction baseline cannot exceed this Automerge save size.
Incremental checkpoint7 KiBOne ordinary hot-storage candidate cannot exceed 7,168 bytes. A later baseline may still be possible.
Candidate storage1 MiB per workspace document epochA document epoch cannot use more candidate bytes than this bound.
Durability checkpoints20 per workspace document per UTC dayFurther new checkpoints wait until the next UTC day. Exact retries of an existing request remain replayable.
Exact receipt3 KiB per rowA durability receipt that cannot fit is refused before a new candidate is written.
Receipt history2 MiB per workspace documentFurther receipt-producing checkpoints are refused when the exact replay ledger is full.
Cloud storage objects130 per hot workspace document epochHot storage uses 129 candidate slots and one pointer. Cold inactive storage uses one object.
Candidate history tail127 entriesCompaction keeps the candidate chain within this bound.
Active operations8 per cloud documentWait for current writes to settle, then retry.
Queued operations2 per connectionWait for the current connection’s queued writes to settle, then retry.

Transport and connection limits

LimitMaximumWhat reaching it means
Binary sync frame196,876 bytesThe individual Automerge transport frame is refused. Large snapshots are normally chunked into smaller frames.
JSON sync frame32 KiBThe individual JSON protocol frame is refused.
Message rate120 frames per connection per minuteWait for the rolling one-minute window, then retry.
Data rate1 MiB per connection per minuteWait for the rolling one-minute window, then retry.
Pending connection data256 KiBA slow or overloaded connection is closed before its unsent queue grows further.
Connection credential lifetime300 secondsActive 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 512 KiB. Your local scenario is unchanged.

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.

The numbers on this page are product limits. Internal parser-allocation safeguards, deployment qualification budgets, and modeled infrastructure assumptions are not user quotas and are intentionally excluded.

Related reading

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.