Forum Discussion
How to use "Auto Recovery" in Storyline 2.0
I have just lost 8 hours work on a Storyline 2.0 project.
I clicked on "Preview Entire Project" and the software aparrently crashed.
It came back with nothing and the page layout and project lay...
Hi L'Oreal,
I'm sorry to hear about your file, and thanks for letting us know that you were also working with our Support engineers and they were able to confirm it was a corrupted file as well.
As mentioned earlier in this thread, you could look for the files here:
1) Open this folder in Windows Explorer: %appdata%\Articulate\Storyline
2) Scan the contents of this folder for a file that starts with the name of your project. If you find one, copy it to your desktop. If you find more than one, copy the latest version to your desktop.
3) Change the file extension of the copy on your desktop from *.tmp to *.story.
4) Double-click the file to open it in Storyline.
File corruption is unpredictable, and there's no straightforward way to determine what causes it. Common causes are environmental (disk errors, power outages, improper shutdowns), viruses, failed Windows updates, and even file size (i.e., very large files have a higher risk of corrupting). Consider these preventative measures to protect your project files:
1) Save and publish projects on your local hard drive. Working on a network drive or external USB drive can cause erratic behavior due to latency.
2) Save your projects periodically as you're working on them and take advantage of Storyline's AutoRecovery feature (http://articulate.fyi/1peyrV4).
3) Install Dropbox. Snapshots of changes in your local Dropbox folder are kept for 30 days. If a file is damaged or deleted, you can restore a previous snapshot: https://www.dropbox.com/help/11/en.
4) Don't leave Storyline open and unattended for long periods of time. Some users have reported file corruption after leaving Storyline open overnight. It's possible that a malware scan or disk backup could run because the machine is idle, making Storyline vulnerable to crashing.
Thanks Ashley for this very useful comment. It took me a while to find these steps.
I suggest if you create a separate thread and list all these steps.
