Forum Discussion

tod2025's avatar
tod2025
Community Member
2 days ago

Next Button Disabled on Resume After Video Completion – Storyline 360

Hi Team,

I have a query related to the Resume behavior in Articulate Storyline 360.

In my project, a slide contains an MP4 video. The Next button is initially disabled and is enabled only after the video completes, which works correctly on the first visit.

However, when the learner closes the course and relaunches it, then clicks Resume, the slide resumes correctly but the Next button appears disabled again, even though the video was already completed earlier.

Requirements:

  • Player: Default Modern Player
  • Navigation:
    • using default navigation, and
    • Alternative solution using custom navigation 

This issue is critical, and I need a reliable solution that ensures the Next button remains enabled on resume once the video has already been completed.

Please advise on the best possible approach to resolve this.

Thank you.

3 Replies

  • I'm guessing you have a trigger to disable NEXT when the timeline starts, and another trigger to enable it when the video is done.

    A “when timeline starts on this slide” triggers runs every time the user reaches the slide—even if the Slide Properties are set to “Resume saved state.” 

    If you don’t want the trigger to run in some situations, you need to add conditions to the trigger.

    • For example, the conditions could check whether the state of buttons on the slide = Visited. Or a condition could check whether a T/F variable = True.
    • In your case, I suggest using a T/F variable. On the disable-Next trigger, add a condition so it only runs when the variable = False.  Set the variable to True when the video ends. 

     

    For more info: TIP: Controlling the NEXT Button 101 | Articulate - Community 

  • tod2025's avatar
    tod2025
    Community Member

    Hi Judy,

    Thank you for your feedback. I’ve reviewed your suggestions and also tested the resource “TIP: Controlling the NEXT Button 101 | Articulate – Community.” Unfortunately, the issue still persists in my case, and the referenced sample file does not behave as expected.

    Here are my observations:

    Option 1:
    After clicking all buttons and relaunching the course, the Resume action takes the learner directly to the third layer instead of the base layer, and the Next button remains disabled.

    Option 2:
    The Next button is enabled, but on revisiting the slide the course resumes on the third layer, not the base layer, which is not the intended behavior.

    Additionally, the sample file you shared does not include an MP4 video. In my project, the issue occurs specifically when a video is used to control the Next button state. Without a video, the behavior works as expected; the problem appears only when video completion is involved.

    I’ve attached my Test files for reference. Please review them and let me know if I’m missing any configuration or if there’s a known limitation when using video-based navigation control with Resume.

    Thank you for your continued support.

  • tod2025​: You may have discovered a bug. 🐛

    I looked at your Test_usingVariable.story file. When I preview it, the Next button works as expected—when I watch the video to the end. However, the video is longer than the timeline of the layer. If I preview it and click Next after the timeline ends but before the video completes, the Next button remains disabled when I return to the slide, even though the variable = True.

    • My best guess: The program gets conflicted between the triggers controlling Next and the Restricted Navigation (which controls Next based on the base timeline). 

     

    The attached file has two edited versions that avoid the bug.

    • One version uses "when the timeline ends on this layer" triggers.
    • One version uses "when the media completes" triggers.
    • In both versions, the timeline of the base was shortened to be less than the length of the video. And the timeline of the layer was extended to match the length of the video.

     

    StevenBenassi​ : I'm just tagging you because there seems to be a bug that should be investigated by the support team.