Forum Discussion
Articulate Storyline "Jump to time" trigger no longer working the same way after the update.
The "Jump to time xx when timeline starts on this slide" is no longer working the way it did before the last update.
Currently I have a trigger set up to "Jump to time 22 seconds when timeline starts on this layer, if xyz variable = true" and then another trigger set to "play audio at 23 seconds" and prior to updating it all worked as expected, however now upon returning to this slide, the player will jump to 22 seconds and then pause, and stay paused.
I have gone through and checked off the "play timeline" checkbox in the triggers, attempted to implement a "resume timeline" trigger on the slide, and even gone back and compared to previous versions of the module saved out before updating, however I run into the same issue there too.
Truthfully I may have left the update a little too long, as I only updated last week and I believe this update was release some months ago..
if anyone has any thoughts or similar experiences please let me know!
I've moved it to a local drive as suggested by the chatbot, and initially I thought that it had worked, but now I'm just getting inconsistent behaviour where sometimes it will progress as intended and other times it freezes up like it was before.
I'll keep investigating.
The plot thickens,
I've exported to SCORM and am reviewing the story file and everything is working as it did previously, leading me to believe that the issue lies with my Storyline install. Perhaps updating broke my install somehow?
Will uninstall and reinstall Storyline and continue testing.
Reinstalling didn't do anything, I got most of the way through reviewing the scorm and came to realise it's mostly random when it works and when it doesn't.
still at a loss.
in the story file, I find that if the timeline does randomly pause after coming back to a slide, I can unpause it by changing tabs and returning to the module, which I shouldn't have to do but it seems to work
Hi Reilly!
It sounds like Triggers from your Storyline course aren't functioning as expected. Sorry to hear that, but I'd be happy to assist!
Thank you for sharing the troubleshooting steps you've implemented so far. To clarify, are you observing this behavior when previewing the course within Storyline, or while viewing the course on an LMS? It would be helpful to have a closer look at the project file itself and test the behavior on our end. Would you mind uploading a copy here in the discussion or privately through a support case?
Looking forward to hearing from you!
Hi Steven!
Apologies, to clarify I experienced this in both the in-app Preview through storyline, as well as reviewing the story file through my browser.It's worth noting however that I did reach out through Live chat and someone Named Fannie May helped me through some of my issues, though not all were solved and I needed to find a workaround for some of it.
Fannie should have a copy of the project file as they were going through it for further testing, as they wanted to test it in older versions of storyline.
as I said to Fannie, the main thing that perplexed me is just that these behaviours have changed since the last update, and the way "jump to time" interacts with slides based on whether they have been set to "reset to initial state" or "automatically decide" seems to be the cause.
Hopefully that makes sense!
curious to hear if this has a resolution as I'm having the same issue. Will check back!
Hi Stephanie,
my slides were set up in a pretty particular way, with animated transition slides which are called when buttons are pressed and so on,
but what I ended up having to do was change the slide behaviour from "reset to initial state" to "Automatically decide" (which wasn't the case, or necessary before the update), rearrange my triggers so that the hide layer - "transition" when timeline starts on this slide, so that it was as high up in the stack as possible, make sure my Transition slide was set to "reset to initial" and push everything forward by 1 second so there was a blank second on the transition for buffering.
and on the last slide of each section where I had a trigger which sets "section complete" to true, making sure that it is called before the trigger which brings up the Navigation.
hopefully that makes sense and is helpful, and I understand that your project may be set up completely differently to mine, but with any luck something in that list helps!
Hi Reilly,
Thank you for sharing the details, I appreciate it and will see if it helps resolve my issues.Stephanie Holm
Training Specialist
Ethics and ComplianceP 615-344-3545
Hi Stephanie!
Please let us know if you have any other questions that arise. We are happy to help!
It looks like part of your email signature came through when you replied via email. You can remove that if needed by clicking ‘Edit’ beneath your response. Here’s a quick Peek video if you need help.
Have a great afternoon!
