'Not enough space on disk' ....can't save work

It's only for 3 projects.  Yes, they appear to be duplicates of the same project.  I deleted most of the files, but here's a screenshot of what it looks like.  As you can see, a large project that keeps duplicating itself will eat up memory really quick.

Thanks CK1 - I added that image and additional information to the report I filed and I'll be in touch here once I hear from our QA team, but in the meantime I'm glad you're able to delete the troublesome files and continue working. 

Good Afternoon, CK1.

Our Engineering Team has helped us to understand how our AutoRecovery feature works.  Here's a summary:

At an interval defined by you (10 minutes by default) Storyline 2 checks to see if the currently open project has been modified and not saved.  If there are unsaved pending changes, an AutoRecovery file is created for the project inside the %USERPROFILE%\AppData\Roaming\Articulate\Storyline\ folder.  This AutoRecovery file is named using a format like this:

<original project name><creation time stamp of the file>.tmp

So, if you were working on a file called "example.story" the AutoRecovery name might look like example635502380729253410.tmp.

As long as the .story project file name doesn't change, Storyline 2 should keep overwriting the same AutoRecovery .tmp file over and over again.  So, if you have a single project open for a long time, it should only result in one simple .tmp file that keeps getting overwritten with the latest AutoRecovery data.  When the project is closed (either by opening a new project, or closing Storyline), then any .tmp file that was created for AutoRecovery purposes should be deleted.  If Storyline crashed or there was an error trying to delete the .tmp file, then it would obviously stick around.

In summary:  As long as the name of the project and the creation timestamp of the project file didn't change, a single project should have only left a single .tmp file behind.  So, even if Storyline 2 was failing to clean up properly, we shouldn't be taking up massive amounts of disk space.

As a result, I have a few clarifying questions:

• Is it possible that you have been making copies of the same project file (or performing the "Save As" function) with a new filename each time?
• Is it possible that you have been making copies of the same project file but keeping the name of the project the same?
• Is it possible that some kind of backup or anti-malware software is manipulating the file creation timestamp on a single project file?
• Are you still experiencing this behavior often?

Thanks in advance for helping us to understand what might be going on with your machine!

I have increased my virtual machine memory size to 100GB and after using Storyline 2 for one week, my memory is completely gone. I can't find the files in the appdata folder; it is storing them somewhere else? Ugh, still having saving issues & client is getting antsy

Hi Wendy,

We released Update 4 of Storyline 2 on Friday which dealt with a number of the issues associated with saving and temp files detailed here. 

I'm having the same problem. The temp files are not purging from the AppData file.... See my screenshot....  And this is not an isolated issue, it keeps happening.  I did not have these problems in SL1.  It's really cutting into my workflow - I would appreciate if there would be another fix to this soon or I will just have to use SL1 to keep working efficiently.

Hi Jon,

We're now on Update 5 of Storyline 2, which you can download here.  Also, the release notes which detail all the fixes are here. 

You can also empty the temp folder, you'll just want to follow the steps here:

1. Open Windows Explorer, type %temp% in the address field, and press Enter.
2. When your temp directory opens, press Ctrl+A to select all the temp files, then press the Delete key on your keyboard.
3. A few temp files may currently be in use that can't be deleted. When prompted, you can skip those.
4. You can now save your project file.

Hi Ashley - I have been having the same problem with a file I'm working on. I have just carried out the temp cleanup (your 4-step process above) and it looked like it was going to work but , right at the end of the save, I now have this error:

The project file could not be saved. There was an error generating the XML document.

I tried saving it with a different name as well but with no luck. Any ideas?

Hi Jane,

Are you also using Update 5 of Storyline 2? I know that specific error message was dealt with as a part of the update so if you're still seeing it I imagine we're going to want to take a look at a sample file. Are you able to see if importing that file into a new one allows it to work well? What about in a brand new file that you've ensured is saved to your local drive? 

I'm having the same issues too I can't even open my project now....this is stressing me out as I'm on very tight deadline....can someone help fix this?