The timer should go away after the learner reaches the results slide, but that's currently not working correctly in Storyline 360. The timer stays on the player specifically in HTML5 output, which means you'll also see it in the Preview of your course.
Besides viewing the Flash output, we don't have a solid workaround yet. I'll keep this discussion updated, though, if I get any new information.
I am also hoping for a solution for this in SL360.
I tested the timer function in Storyline 2 it actually works as intended. The timer removes itself as soon as the learner navigates away from the results slide.
I am embarrassed to share how often I end up resorting to older version of Storyline just to get basic things to function as intended. I have also used older versions of Storyline because of a keyboard accessibility bug that has been brought up and unresolved for several months.
I'm sorry you've run into the same issue, and this is still with our team to investigate. We'll keep you posted on that here as we've linked the forum discussion.
I didn't see a forum discussion you were in about a keyboard accessibility issue, but I'd love to follow up on that for you. Can you share any more details or link me to that discussion?
Hey Ashley. The keyboard accessibility issue that I am referring to was brought up to the support staff (Case #01582111) in late November last year. I've been told that it has been "logged it as a possible software bug" and that it might take a long time to be resolved.
In many situations I've been forced to use an older software build where the keyboard accessibility feature was functioning as intended. This is, as you could imagine, quite often.
The last working SL360 build that is functioning properly in terms of keyboard accessibility dates back to August 2018 (3.19.16600.0). The recent feature that lets us revert back and forth between builds has been helpful to me recently, but also means that I am forced to run older versions and deal with bugs that have been patched in newer versions. This is becoming increasingly difficult to deal with as more and more bugs result from new SL versions.
Thanks for sharing your case number, Tyler, and I'm sorry you're in a tough spot.
I checked in on the keyboard accessibility bug, and it's on our priority list for a fix. We recognize this bug makes courses essentially unusable for people using a keyboard to navigate, so we're working to sort this out.
I'll come back to this discussion to let you know as soon as it's resolved.
Also, sorry for hi-jacking this thread. I still believe that the timer issue is still very important to have worked out. For anybody who happens to have Storyline 2 and is okay with using it for their project, the timer works as intended in this version. I believe it should also work in SL1 but haven't tested SL1 for myself.
I've run into this issue again today and I realized that there is another separate (possibly linked) issue with the timer.
Say the timer is set for 1 minute. When the user goes through the quiz the first time, the allotted time limit works as intended, even though it stays visible even after the quiz is completed.
Say that the user doesn't pass, and we want to allow them to retry. If I do that, then the timer resets, but doesn't stop on the results slide. Instead it keeps going even if the user had already passed the results slide and are on a different scene than the quiz scene. After 1 minute (and after they had already passed), they get interrupted in the middle of where-ever else they had made it to in the learning object with a message saying "Time Limit Exceeded" even though they had already passed the timed quiz activity.
Please fix this Articulate. These issues never existed in SL1 or SL2.
Edit: this issue only happens in my current project. If I start a new project with a quiz, timer, and results slide, the timer does not keep going on the second attempt. I just need to figure out how to fix my current project now without re-doing everything...
Does this happen in the published output, during Preview, or both?
Would you mind sharing the affected .story file with us? It'll help us get a clear picture of what's happening, and we'll delete it after troubleshooting. You can send that file to us privately in a case here.
Thanks for the response! I actually ended up figuring it out.
I was using a trigger to "Jump to next slide when timeline starts" on the correct layer in the Results slide. My intention was to forward the user to a custom made "Congratulations" Scene if the learner completes the activity correctly.
When I remove the trigger to "Jump to next slide when timeline starts" the timer does actually stop on the results slide as intended after the second attempt. So now I just changed it to "Jump to next slide when timeline ends" and set to timeline to only take 1 second, just enough time for it to register and stop the timer.
The funny thing is that the issue never exists on the first attempt, this only happens the second time around for some reason. In any case, I got it working again.
I'm currently working on a project with several timed quizzes and the older timer hangs around until the new timer starts, The new timer does replace the older but the fact the user still sees the older timer is an issue.
I really hope there's at least a work around for this.
Hi - We are in the process of completing the design of a really exciting timed problem solving module and are using the timer. However the lingering timer is proving a real showstopper from a learner experience perspective.
Reading through this thread is it seems it has been under investigation for quite some time and it's disappointing that a resolution hasn't been implemented yet.
Can anyone from the Support Team give an update or suggest a workaround that would hide the timer after the associated challenge / quiz is complete?
Thanks for following up. I'm sorry that you ran into the issue where:
Timer graphic persists on the player throughout the course navigation after the results slide is viewed.
It is still currently in the early stages of review based on our How We Tackle Bugs article. To help you plan, it's unlikely to be fixed in the next couple of updates.
Update 43 for Storyline 360 is ready: We fixed the issue where a timer could continue to display after moving past a quiz, and sometimes the "time limit exceeded" message would appear on a result slide.
23 Replies
Hi there Jennifer!
The timer should go away after the learner reaches the results slide, but that's currently not working correctly in Storyline 360. The timer stays on the player specifically in HTML5 output, which means you'll also see it in the Preview of your course.
Besides viewing the Flash output, we don't have a solid workaround yet. I'll keep this discussion updated, though, if I get any new information.
Thanks, Alyssa.
Hoping for a quick resolution. Flash isn’t an option for us.
Thanks.
Jennifer K. Snyder
I am also hoping for a solution for this in SL360.
I tested the timer function in Storyline 2 it actually works as intended. The timer removes itself as soon as the learner navigates away from the results slide.
I am embarrassed to share how often I end up resorting to older version of Storyline just to get basic things to function as intended. I have also used older versions of Storyline because of a keyboard accessibility bug that has been brought up and unresolved for several months.
Hi Tyler,
I'm sorry you've run into the same issue, and this is still with our team to investigate. We'll keep you posted on that here as we've linked the forum discussion.
I didn't see a forum discussion you were in about a keyboard accessibility issue, but I'd love to follow up on that for you. Can you share any more details or link me to that discussion?
Hey Ashley. The keyboard accessibility issue that I am referring to was brought up to the support staff (Case #01582111) in late November last year. I've been told that it has been "logged it as a possible software bug" and that it might take a long time to be resolved.
In many situations I've been forced to use an older software build where the keyboard accessibility feature was functioning as intended. This is, as you could imagine, quite often.
The last working SL360 build that is functioning properly in terms of keyboard accessibility dates back to August 2018 (3.19.16600.0). The recent feature that lets us revert back and forth between builds has been helpful to me recently, but also means that I am forced to run older versions and deal with bugs that have been patched in newer versions. This is becoming increasingly difficult to deal with as more and more bugs result from new SL versions.
Thanks for sharing your case number, Tyler, and I'm sorry you're in a tough spot.
I checked in on the keyboard accessibility bug, and it's on our priority list for a fix. We recognize this bug makes courses essentially unusable for people using a keyboard to navigate, so we're working to sort this out.
I'll come back to this discussion to let you know as soon as it's resolved.
Thanks for the update Alyssa!
Also, sorry for hi-jacking this thread. I still believe that the timer issue is still very important to have worked out. For anybody who happens to have Storyline 2 and is okay with using it for their project, the timer works as intended in this version. I believe it should also work in SL1 but haven't tested SL1 for myself.
I hear you, Tyler. And no worries on bringing up a new topic in this discussion. We'll do what we can to help answer any questions you have!
Hi Tyler,
Great news! We just released another update for Articulate 360 and included a few important fixes that you'll see in the release notes here.
The item you'll be interested in is:
When using the modern player, the keyboard navigation didn't always work after resuming the course.
Just launch the Articulate 360 desktop app on your computer and click the Update button for Storyline 360. Details here.
Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.
That's great news! Thanks Leslie!
I've republished my project and the keyboard navigation is now working again!
Thanks for confirming, Tyler.
Glad to hear it's working as expected for you now.
Hi Alyssa, is there any progress on solving the issue of "timer stays on the player specifically in HTML5 output"?
Hi Joanne. This issue is still open with our team, and we're tracking the impact. We'll be sure to update you here with any changes!
Thanks Crystal, I really need that be solved in one of my current project. There's no problem in Flash output but Flash has become a past.
So this discussion is a year old now. Any update in removing the timer in player after quiz is complete? It's very confusing to learners.
Hi Tyler,
I do not have an update, but we are tracking the user impact as Crystal shared above.
I've updated this impact based on the additional comments here.
This conversation is attached so that we can share any information with you here.
I've run into this issue again today and I realized that there is another separate (possibly linked) issue with the timer.
Say the timer is set for 1 minute. When the user goes through the quiz the first time, the allotted time limit works as intended, even though it stays visible even after the quiz is completed.
Say that the user doesn't pass, and we want to allow them to retry. If I do that, then the timer resets, but doesn't stop on the results slide. Instead it keeps going even if the user had already passed the results slide and are on a different scene than the quiz scene. After 1 minute (and after they had already passed), they get interrupted in the middle of where-ever else they had made it to in the learning object with a message saying "Time Limit Exceeded" even though they had already passed the timed quiz activity.
Please fix this Articulate. These issues never existed in SL1 or SL2.
Edit: this issue only happens in my current project. If I start a new project with a quiz, timer, and results slide, the timer does not keep going on the second attempt. I just need to figure out how to fix my current project now without re-doing everything...
Oh no, Tyler!
Sorry to hear this problem is happening with a specific file. I'm happy to help you investigate and have a few clarifying questions:
Hey Katie,
Thanks for the response! I actually ended up figuring it out.
I was using a trigger to "Jump to next slide when timeline starts" on the correct layer in the Results slide. My intention was to forward the user to a custom made "Congratulations" Scene if the learner completes the activity correctly.
When I remove the trigger to "Jump to next slide when timeline starts" the timer does actually stop on the results slide as intended after the second attempt. So now I just changed it to "Jump to next slide when timeline ends" and set to timeline to only take 1 second, just enough time for it to register and stop the timer.
The funny thing is that the issue never exists on the first attempt, this only happens the second time around for some reason. In any case, I got it working again.
Thanks for your concern!
Hi is there any resoltuion to this yet?
I'm currently working on a project with several timed quizzes and the older timer hangs around until the new timer starts, The new timer does replace the older but the fact the user still sees the older timer is an issue.
I really hope there's at least a work around for this.
Hi - We are in the process of completing the design of a really exciting timed problem solving module and are using the timer. However the lingering timer is proving a real showstopper from a learner experience perspective.
Reading through this thread is it seems it has been under investigation for quite some time and it's disappointing that a resolution hasn't been implemented yet.
Can anyone from the Support Team give an update or suggest a workaround that would hide the timer after the associated challenge / quiz is complete?
Hi Tom and Al,
Happy Tuesday, all!
Update 43 for Storyline 360 is ready: We fixed the issue where a timer could continue to display after moving past a quiz, and sometimes the "time limit exceeded" message would appear on a result slide.
Thanks for helping us make this improvement!
This discussion is closed. You can start a new discussion or contact Articulate Support.