Forum Discussion
Storyline issue – Layer not persisting during review since recent updates
Hi everyone,
I have some great news to share.
We just released another update for Storyline 360 (Build 3.114.36655.0), and this includes a fix for the issue you encountered where layers set to “Hide other layers” didn’t behave as expected when revisiting a slide.
This was related to slide layers not maintaining their expected behavior after a slide revisit, and it has now been resolved.
To take advantage of this update, please open the Articulate 360 desktop app on your computer and click the Update button next to Storyline 360. You can find step-by-step instructions here.
SafeTeamAcademy, I especially appreciate you sharing the impact this had on your team’s timelines. I can understand how challenging it is to spend time investigating something internally before confirming it’s tied to a product issue. Thanks as well for your feedback on proactive communication, it’s really valuable and something we’re continuing to look at improving.
Please let me know if you’re still seeing any trouble after updating or if you have any questions!
Hi SafeTeamAcademy,
Thanks for the detailed breakdown, I can see how this would be frustrating, especially since your setup was working as expected before.
I also appreciate NateMarshall-91 chiming in and sharing what your team is seeing. Based on testing and similar reports, this behavior is related to a bug in the latest Storyline update (Update 114), particularly affecting how layers behave when revisiting a slide.
Specifically, there’s an issue where layers set to “Hide other slide layers” don’t behave as expected after a slide is revisited, which aligns with what you’re seeing with your “Lock” layer not persisting and the Next button becoming available again.
This worked correctly in previous versions, so it’s not related to your setup or trigger logic.
This has been reported to our product team and is currently under investigation.
In the meantime, a possible workaround is to revert to a previous version of Storyline (Build 3.113), where this behavior works as expected.
Hello EricSantos,
Indeed, we reverted to a previous version this morning (3.113), and everything is working properly again. Thank you! 🙂
Please feel free to keep us informed once the issue is resolved in a future update.
We would also like to share that investigating this issue internally, before identifying it as a Storyline bug, required several days of work and impacted our timelines. In that regard, it could be very helpful for us if known issues or bug reports were communicated proactively, as it would help avoid unnecessary investigations and reassure teams when unexpected behavior occurs.
Thank you again for your support and for the valuable feedback you always provide.