Inkscape write retry behavior and duplicate file prevention

Goal: Determine whether Inkscape provides a built‑in retry mechanism for write operations that avoids creating duplicate or partial SVG files when saving to unreliable storage.

Context: Users often save SVG documents to network shares or removable media that may experience transient connection drops. When a write fails, it is unclear if Inkscape automatically retries the operation, whether it overwrites the same file or creates a temporary copy, and what cleanup occurs if the retry succeeds after an initial failure.

Constraints: Any retry behavior must not leave behind partial or duplicate SVG files, must preserve the integrity of the original file, and should not require manual intervention to remove stray files.

Questions: Does Inkscape automatically retry a failed save, and if so, how does it handle the target file during retries? Is there a setting to control the retry count or to enable an atomic write‑replace approach? Are duplicate or temporary files ever left behind when a retry succeeds after an initial failure?