Auto-recover file problem

Hello,  I imported a little powerpoint into Storyline, added more slides, changed a lot of things.  I save frequently.  Then Storyline crashed without explanation.  When I reopened the file it said it was auto-recovered and told me to save the changes.  But the changes are bad.  But there doesn't seem to be a way to get back to the last version that I saved (which wasn't very long ago.) :(

5 Replies
Leslie McKerchie

Hi Alison,

I know that must be frustrating, but let's see if I can offer a couple of things to help.

There may still be a working version of your project 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. 

You can also adjust how often the AutoRecovery saves in your Storyline Options.

Alison Coops

Well, that might help in a different circumstance (although almost everything in that folder is from 2017).  The problem wasn't that the autorecover file was old, it was corrupted. So not only did I have to redo all of the changes I had made (which seemed to go back substantially before the last time I had saved) but I also had to fix things which had never been broken before.  I've done all of this now, but I hope your techies can figure out what went wrong so it doesn't happen to me or anyone else in the future. When there's a crash in a Microsoft program it asks if you want to open the last version saved by user (with a date and time) or the last autosave (with a date and time).  I would have picked the last by user which was only a few minutes before, but there was no way to get back to that.  The corrupted autosave seemed to have replaced it.

Leslie McKerchie

Thanks for the additional details, Alison. 

Are you working locally with your software, assets, and files? This is typically your C: Drive.

Curious if you have had this issue happen in any other course or just this particular one?

If just this course, you may want to consider importing the file into a new one.

If it's happening in any/all files, you should conduct a repair of your software.