What has happened to AutoRecovery
Mar 06, 2023
I've just lost a couple of hours work.
I have my projects set to Save AutoRecovery every 10 minutes.
When I went to save my project it crashed.
I then re-open the project and the usual AutoRecovery message is not appearing.
I check the "AppData\Local\Articulate\360\ProjectBackups\" folder, and a file is there with the current date and time, and the project name.
I open the file, and there are none of the additions. Just the same old file but with a new modified date/time.
This is not an isolated incident, it has happened multiple times in the past 2-3 weeks and so appears to be a bug as I have been able to rely on the AutoRecovery up until this point.
The major issue is, the crash occurs on Save, and therefore there is a good chance I am going to lose work unless I perform a Save-As which seems reliable.
Two issues:
- Crash frequently occurs when Saving a project
- AutoRecovery is no longer working for me.
I note in Feb there was an update to "Enhanced Project Recovery". It could be a coincidence, but seems to much of a coincidence to me as it seems to correspond with the period I have been experiencing losing work.
1 Reply
Hello Sam,
Sorry to hear about your experience with your project files.
The first thing I'd like to address is the frequency at which you are encountering these crashes. I'd like to ask a few questions to help clarify your experience:
Additionally, you can also check for working copies of your project file in your temp files. Here's how to check:
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.
Check out this article to know more about common causes of file corruption, as well as how to address them.
If you're already working locally when making changes to your project, try doing a repair of Storyline 360 to see if this fixes the behavior. If the issue persists, open a case with our support team here so we can take a closer look at what's happening with your project files.