Search functionality not working after Storyline update

Feb 06, 2020

Hi everyone,

Our team recently discovered that the search functionality in our projects no longer works after publishing with the latest version of Storyline.

It seems to be a bug that was introduced with the January 21, 2020 (Build 3.36.21213.0) update because we were able to get it back by reverting to the December 19, 2019 (Build 3.35.21017.0) version and republishing.

We've already submitted a ticket, but I wanted to post here as a heads up to others who might not be aware. Has anyone else encountered this after installing the January 21 or January 28 update?

19 Replies
Kristin Kushner

Hi Leslie! Thanks for the response. I have already submitted a ticket on this issue (#02146798), and they have submitted it as a bug.

Basically, in the latest version of Storyline, search only works for slides made visible in the menu. We hid slides in our menu, so search stopped working for those slides.

We are hoping a fix can be put in place so we don't have to rework all of our courses/keep uninstalling/reinstalling different versions of  the tool.

Leslie McKerchie

Hi CK1,

Do you know what version of Storyline you're using?

You can check by going to:
Help > About Articulate Storyline

We are currently on Build 3.40.22208.0 of Storyline 360. You can read all of the details here.

We have this marked as resolved in Build 39, but if you're still having difficulty we would be happy to take a look.

Lauren Connelly

Hi everyone!

We appreciate your updates on this issue! I'm excited to report that we've released the fix in today's update for Storyline 360!

Fixed: In some cases, the search feature worked inconsistently. In others, learners could use the search feature to jump to unvisited slides when menu navigation was restricted or locked.

All you need to do is update your Articulate 360 desktop app to make sure you're using Storyline 360 Update 41 (Build 3.41.22450.0)! Head over here to see what other features and fixes are included in the version.

This discussion is closed. You can start a new discussion or contact Articulate Support.