Forum Discussion

SafeTeamAcademy's avatar
SafeTeamAcademy
Community Member
22 days ago
Solved

Storyline issue – Layer not persisting during review since recent updates

Hello everyone, I’m encountering an issue in Storyline that seems to have appeared after the most recent updates. Context: I’m using a question slide with: one Correct layer one Incorrect...
Articulate 360
Review 360
storyline 360
  • EricSantos's avatar
    EricSantos
    19 days ago

    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!

KelleyConrad's avatar
KelleyConrad
Community Member
20 days ago

I'm having several issues with the latest version and had to revert to the prior version. Audio doesn't play correctly on layers, triggers are inconsistent, layers don't work as expected, etc.

  • SafeTeamAcademy's avatar
    SafeTeamAcademy
    Community Member
    20 days ago

    Hello KelleyConrad​

    You’re absolutely right to flag this.

    From our perspective, it would indeed be very helpful if customers were proactively informed when known issues or regressions are identified in a new update. In our case, we spent several days investigating these malfunctions internally (audio on layers, inconsistent triggers, unexpected layer behavior), which significantly delayed our production timelines before we were able to confirm that the root cause was linked to a recent update.

    Having earlier visibility on known bugs would allow teams like ours to quickly rule out internal configuration issues and adapt accordingly, rather than losing valuable time troubleshooting.

    Thanks again for your additionnal message !