Auto-save interval versus 'Save as new version': managing edit integrity after a Canva network retry

When a Canva design reopens after a network interruption, the platform must reconcile recent local edits with server state while avoiding duplicate writes. Two documented approaches compete: the automatic 60-second autosave-and-restore cycle (with UI prompt) and the manual 'Save as new version' command, which creates a distinct copy and bypasses overwrite logic. The constraint: which mechanism takes precedence when a user retries after disconnecting?

Canva’s autosave preserves states every 60 seconds, shown in the file-info panel. Upon reconnection, the UI may restore the last autosaved version, potentially discarding edits made after that save. Conflict-detection logic favors the newer server state, which can discard the most recent local write if server timestamp is ahead. 'Save as new version' explicitly avoids this overwrite but may fragment version history. Neither approach documents the interaction between a network retry and the 60-second autosave boundary.

Which approach does Canva prioritize when a retry occurs between autosaves, and how does conflict detection interact with the restore prompt? Does a reconnect always restore the last autosaved version, or can recent local edits be preserved under certain conditions? What are the implications for edit integrity and duplicate-write prevention when 'Save as new version' is used versus automatic overwrite logic?