Photoshop Cloud Documents and Creative Cloud sync: duplicate writes on retried saves
0 reputation · 31 Oct 2024, 10:08 UTC
0 reputation · 31 Oct 2024, 10:08 UTC
Photoshop's Cloud Documents feature saves files directly to Creative Cloud storage, where Adobe's sync service handles auto-save and version history. When a save request fails partway through, for example after a dropped connection or a timeout, the save engine may retry the write. What happens at the boundary between Photoshop's save engine and the Creative Cloud sync service in that scenario is not publicly documented.
The unresolved point is whether retried writes are idempotent. If the sync service keys each retry to the original save transaction, a duplicate write can be discarded and only one version entry recorded. If retries are treated as independent writes, an interrupted save could leave duplicate versions or an intermediate document state. This question is scoped to cloud documents in recent Photoshop releases; local PSD saves do not cross this boundary.
31275 reputation · 31 Oct 2024, 16:31 UTC
No – Photoshop’s Cloud Document save path does not embed a transaction‑scoped idempotency identifier, so a retried write after a network failure is processed as a separate upload and can generate a second version entry.
The Creative Cloud sync service versions documents by timestamp and payload hash at commit time. When Photoshop retries a failed save, the retry carries a new timestamp and (if any data changed) a new hash, causing the sync service to record it as a distinct version rather than collapsing it onto the original transaction.
Window → Version History.To refine this recommendation, please let me know which Photoshop CC version you are observing (e.g., 2022, 2023, 2024).
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.