Ever since the most recent update, previewing the project in the editor causes the file to close. This only seems to occur when I preview twice w/o making changes between the previews.
\n
When the timeline completes, the program behaves as though I closed the window or pressed ALT + F4:
\n
\n- If there are no unsaved changes, the project will close.
\n- If there are unsaved changes, I'll get the message asking if I want to save. If I click Yes or No, the project will close. If I click Cancel, I can resume editing as normal.
\n
\n
It does not appear to be related to a specific project. It happens even with new, unedited file. You can see a screencap video of the issue attached and here: Preview closes project
Ever since the most recent update, previewing the project in the editor causes the file to close. This only seems to occur when I preview twice w/o making changes between the previews.
\n
When the timeline completes, the program behaves as though I closed the window or pressed ALT + F4:
\n
\n- If there are no unsaved changes, the project will close.
\n- If there are unsaved changes, I'll get the message asking if I want to save. If I click Yes or No, the project will close. If I click Cancel, I can resume editing as normal.
\n
\n
It does not appear to be related to a specific project. It happens even with new, unedited file. You can see a screencap video of the issue attached and here: Preview closes project
I was also faced the same issue in v3.53. But the issue has been resolved with the latest update v3.54. Try to update your software.
\n
Thanks...
Update your storyline to .25674.0 released yesterday,
Thanks for confirming that the latest version resolved the issue for you, Rahul and Soren.
Adding my two cents here since the updates of two months ago did nothing to correct this for me... I'm working in a fully updated version of Storyline and this is continuing to happen. It's (quite) annoying since the play and pause features (and use of the spacebar) within the timeline is obviously the most common way to manipulate animations and timing when you're building a course. Just yesterday, I was distracted while working quickly and mistakenly closed a file that I didn't mean to close. And, even though I have Storyline set to save my work every minute, this prompt will override the autosave and won't capture any of the changes made during the working session. Can someone from Articulate explain the rationale for this? And why isn't the repair working for all 360 users?
Oh dear. What good is the auto save feature then if it doesn't autosave in a predictable way?
\n
But there are way too many old niggles with Storyline right now that has been lingering for years without any change in sight. It is as if we only get features that can be made into USPs on a powerpoint slide right now. So many Quality-of-Life fixes that this software could really benefit from if it was prioritized. Actually auto saving Auto save is one!
Hi Kate,
\n
Thanks for sharing that you're still having an issue.
\n
I'm working in a fully updated version of Storyline and this is continuing to happen.
\n
Can you share what version of Storyline you're using?
\n
\n- You can check by going to Help > About Articulate Storyline
\n
\n
Even though I have Storyline set to save my work every minute, this prompt will override the autosave and won't capture any of the changes made during the working session. Can someone from Articulate explain the rationale for this?
\n
The AutoRecovery setting in Storyline 360 is not an auto-save feature. Here are the details:
\n
Storyline will automatically save a copy of your project at the specified interval (after you’ve saved it at least once). The default interval is every 10 minutes, but you can enter any whole number between 1 and 120. If Storyline closes unexpectedly, you’ll be prompted to recover your project the next time you open it.
\n
Storyline 360: Setting Storyline Options
\n
There may still be a working version of your project in your temp files. Here's how to check:
\n
\n- Open this folder in Windows Explorer: %appdata%\\Articulate\\Storyline
\n- 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.
\n- Change the file extension of the copy on your desktop from *.tmp to *.story.
\n- Double-click the file to open it in Storyline.
\n
\n
Why isn't the repair working for all 360 users?
\n
I'd like you to share your project file with our support engineers to investigate what's happening with your permission. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.
Thanks for the reply, Leslie.
I am working in v3.56.26145.0.
And, yes, I understand how the auto-recovery feature works and am grateful for it in most instances. Unfortunately, since the spacebar prompt issue is different (i.e. not the result of an unexpected crash or file shutting down) - since I clicked \"ok\" without recognizing what the message was asking, it doesn't really apply here.
I did try to find the file in my temp files folder but alas keep getting the \"This process is locked/You don't have access to this\" message. (I'm paraphrasing the message, but I'm sure you recognize the one.)
I have rebuilt my file with the lost work and of course, the material is proprietary and highly regulated so I'm not able to share it. If this happens again, I'll save my file and sanitize the proprietary info so your support team can have a look.
\n
Thanks again for the reply.
This started happening last night for me as well. But only on certain files. It is super annoying and I can't figure out what's causing it.
Hi Jodi!
Thanks for reaching out! So sorry to hear you are running into this issue with previewing and publishing. I understand how frustrating that can be.
\n
I see you opened a support case and you are working with my colleague Lejan. Good call, you're in great hands!
\n
We'll continue the conversation over in the support case as she looks at your file!
\n
Have a great start to your week!
