Forum Discussion
Storyline Glitches - Changes Not Saving, Things Disappearing
I am at a point where I feel like SL is gaslighting me. I know my team has been having ongoing issues for months now, but I am wondering if we are all collectively hallucinating or if this is a larger issue.
We have been having the following issues:
- Making changes to the story file, saving the file, and having the changes revert. E.g., changing the seek bar to locked in the player, removing slides from the menu view, changing audio files, editing text, etc. When we publish after making the changes, the changes will no longer be there.
- Triggers disappearing. E.g., creating a trigger to prevent a slide from moving forward, saving and publishing the course, the trigger is no longer there.
- Entire scenes disappearing after the tool crashes.
- Functions and triggers are not working in preview the way they should consistently.
SL in general is crashing more and glitching more, but those are the biggest things we have been struggling with.
7 Replies
Hi ChelseaEvans-03!
So sorry to hear you and your team are facing these setbacks while authoring in Storyline!
All of the incidents you've mentioned can be caused by working directly off of a network, or shared drive. We always suggest conducting your authoring with files that are stored on your local hard drive. However, if you're already working locally yet still seeing this behavior, please try a repair of your Storyline installation.
If you're still struggling after those steps, it would be helpful to see a copy of a .story file that's been giving you trouble. Feel free to upload that here in the discussion, or privately through a support case.
Let me know how it goes!
Thought it was just me, same for last 2 days, no change to set up, working off local drive, plenty of space left, very frustrating, also cannot share outside of organisation and a reinstall will be a real pain.
I'm sorry you're also going through it! I opened a file yesterday to discover that every single trigger had be ruined. Like on every single slide every single trigger was unassigned. "emphasize *unassigned* using *unassigned* when the timeline reaches 28 seconds". I had to just close the file and walk away.
Our files are saved on OneDrive, typically, but in the last 7+ years of ID work, I've never had issues like this while working from OneDrive. My installation is just fine, and this has been going on for several, several months now across my entire team.
I am not allowed to share proprietary content outside of the company.
