Forum Discussion
Significant lag in NEXT button availability with no triggers
Is there any reason why there is a lag with the NEXT button becoming available for learners? And how can this be fixed?
Course is built in 360, the lag is evident in Review 360 and in the SCORM uploaded to the LMS - using either Chrome or Edge.
There are no triggers on the slides. The NEXT button should be available immediately, however it appears greyed out for anywhere from several seconds to a few minutes.
This affects slides that have text only and no layers or triggers, and is much worse on slides that contain video content. Tried reducing video quality for publication to SCORM but no change.
Participants are reporting the course is 'broken' as they can't immediately progress, and there doesn't appear to be any consistency or reliability in why there is a delay for the NEXT button to be available.
Hi Gillian,
Sorry to hear that you ran into this issue. I'd like to ask a few questions to help clarify your experience:
- Are you working locally when making changes and publishing your project file?
- Have you tried importing your slides to a new project file and checking the responsiveness of the course?
- Are you able to replicate the behavior when using any browser?
Additionally, would you be willing to upload a copy of your course here or in private by opening a support case so we can try to replicate the behavior on our end?
Hi Joe:
Yes, I am working locally.
Yes it has been brought into a new project. And it was working win the old project, and published to LMS however still with a delay on slides.
I have access to Chrome and Edge - no difference. It was replicated also for another person.
I'll send the package through in a support case.
ThanksHi Gillian,
Thank you for the additional information! We'll look out for your file in a support case. Please let me know if you need assistance in the meantime!
Hi Kelly:
I did log a job but have had no contact. I did however figure out my own work around and applied that. It is only a work around and does not fix the more global issue.
Thanks,
Hello Gillian,
I'm glad to hear you found a workaround but I'd like to have our Support Engineers take a look at your project file to investigate further. I have opened a support case on your behalf.
You should be hearing from our staff shortly via email. We'll continue the conversation over there. You are in good hands!
I just wanted to add a quick note as well: it looks like your signature came through when you replied via email. You can remove it by clicking ‘Edit’ below your response. Here’s a quick Peek 360 video if you need help.
Have a great afternoon!
It sounds like the file has Restricted navigation, which automatically disables the NEXT button until the timeline finishes playing.
If that's the case, the simple fix is to switch to Free navigation in the Player:
Thanks Judy. The menu is restricted to ensure all content is completed. Free navigation means having to remove the menu.
Well, as noted above, the NEXT button will automatically disable until the timeline ends when the navigation is restricted.
A few workarounds: Shorten every timeline as much as possible. Or add a trigger on every slide to enable the NEXT button right away. (A trigger will override the auto-disabling done by restricted nav.)
