Articles on: Cloud Storage

What does the File Version Conflict notification mean?

If Scriptation shows a "File Version Conflict" message when you open a cloud file, it means the locally-saved version on your device doesn't match what your cloud provider has stored. The message lets you choose which version to keep.


When you work with cloud files, this message appears when the file was changed or edited outside of Scriptation on your current device — usually from another device or from another app like Finder.


Which option should I select?


  • Tap Keep current version to continue working on your local copy — but be aware that the cloud version is now out of sync, and a conflicted copy will likely appear;
  • Tap Replace with cloud version to discard unsaved local changes and pull down the cloud version;
  • Tap Keep both versions to force a conflicted copy of the local version so you can select which draft to continue working on.


When in doubt, Keep current version is the safest choice — it keeps your local copy and annotations intact.


After choosing either option, manually refresh your cloud folders by dragging your finger down in the File Browser. This forces a manual sync and shows the Loading Content message.



📝 NOTE: Cloud providers occasionally have sync hiccups unrelated to Scriptation or your device. If you end up in a loop where this message won't go away, make a copy of your file and give it a new name.


✅ TIP: A conflicted copy is actually a good thing — your most recent changes are preserved in a fresh, separately-saved file.


Repeated prompts, especially offline or on poor connections


Some users — particularly those working in airplane mode or with spotty on-set Wi-Fi — report the File Version Conflict prompt firing repeatedly, sometimes every time they switch tabs, even when the file has only ever been edited on that one device. This is a known issue our engineering team is actively investigating; we don't yet have a confirmed root cause, but it's a top priority.


If you're seeing this loop:


  • Tap Keep Current rather than Update/Replace — Update can pull a stale cloud version over your local annotations, which is the worst-case outcome.
  • Work locally to avoid it entirely: move the scripts you need into a folder under On My iPad before you go offline, work from that local copy all day, then move (or copy) the updated files back to your cloud folder once you're back on a solid connection. See Moving or copying your files to the cloud.
  • Periodically confirm your work is syncing: use the three-dot menu (⋯) next to a file in the File Browser and select Sync to Cloud to manually push your latest version, or switch away from Scriptation and back to confirm your most recent notes are still there.
  • If it keeps happening, a short screen recording of the prompt firing (through our Troubleshooting Portal) along with your Scriptation version, device model, and OS version helps our team track down the cause.


What's Next


How do I avoid conflicted copies with multiple devices of my own?
I got a pop-up when opening a cloud file. Do I tap Restore or Delete?
How do I manually push a file to my cloud?

Updated on: 31/07/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!