Sketch 93 optimistic locking: symbol merge conflicts blocking concurrent edits on shared Cloud documents
0 reputation · 14 Mar 2026, 17:39 UTC
0 reputation · 14 Mar 2026, 17:39 UTC
Our team collaborates on a shared Sketch Cloud document with a large symbol library. Since moving to Sketch 93, which introduced optimistic locking for symbol instances, we occasionally hit merge conflicts that require manual resolution when two editors touch the same page at once.
The document was originally created in a pre-2018 .sketch format and later migrated, and we are unsure whether the legacy file structure (which predates concurrent-edit metadata) is contributing to slower sync and more frequent conflicts than we would see in a natively modern document.
We want to decide whether to rebuild the document in the current format, restructure the symbol library, or adjust our editing workflow to reduce simultaneous edits on the same page.
Is the legacy file format a documented factor in concurrent-edit sync performance, or is conflict frequency driven purely by symbol count and edit overlap? Is there a supported way to reduce manual merge resolution without disabling concurrent editing? Would splitting the library from the working document change the locking behavior in version 93 and later?
35275 reputation · 14 Mar 2026, 21:16 UTC
Sketch 93’s optimistic locking works at the symbol‑instance level. The file format itself – pre‑2018 versus the current .sketch format – does not change the locking algorithm. What the legacy format does affect is how the Cloud sync engine aggregates changes. Older documents lack per‑object version vectors, so the engine falls back to whole‑document merge checks. This can make conflict detection slower and produce less granular conflict reports, but it does not increase the number of conflicts that arise when two people edit the same object.
Check whether overridden properties are being edited by multiple users. If so, consider moving those overrides back to the library master or using a dedicated “review” page that is not part of the main design flow.
If you want a more precise recommendation, let us know how many users typically edit the same page at once and whether they are changing overridden properties or just the master symbol. This can help decide if a stricter page‑level lock is warranted.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.