Exit Button is Not Working

Hi all

I have a Doubt with Exit Course Trigger, whether I use a custom button with the exit course trigger it is working on Chrome, IE Browsers but it is not working on Firefox Browser. I have tried with different methods still it not working on Firefox. Is that a Browser Problem?

If Anyone Know please suggest me. Thank you.


Siva G

57 Replies
Katie Riggio

Hi there, Lisa!

I see you and Chino, one of our Support Engineers, are already knee-deep in troubleshooting. In fact, I see he's going to have a screen sharing session with you shortly to test the course in another LMS environment right by your side.

You're in excellent hands, and we're also here if you have any questions!

Lauren Connelly

Hi Infra!

Thanks for bringing this to our attention! Are you noticing the same error when publishing the course to the web or LMS? Also, have you tried other browsers such as FireFox?

It would be helpful to take a look at your file. Would you mind sharing it with us? You can do so by using the "add attachment" button in this discussion. Or you can share the file privately with our Support Engineers by using this link.

Lauren Connelly

Quickly jumping into this discussion to give you an update on this bug where the Exit Course trigger wasn't working properly in a variety of browsers!

Good news! We've released the fix in the most recent update for Storyline 360 (Update 36; Build 3.36.21213.0). To keep up with the newest features and bug fixes, you'll need to update the Articulate 360 Desktop App!

Katie Riggio

Hi, Diana! Hi, Luke!

I appreciate you both replying with your findings, and I'm happy to explore further. Based on your details, it sounds like we may have two different bugs here:

  • Diana: Is this happening in mobile or desktop browsers? We have an open issue where the Exit course trigger does not work when viewing published Web content on mobile browsers.
  • Luke: There's an open issue where the Exit course trigger does not work when published to Tin Can. As we continue to investigate, we found that launching the course in a new window helps avoid this bug. 

Let me know if those descriptions don't hit the mark. If it's possible for each of you to share your file with us, we can offer more 1:1 support. You can use this secure upload link!

Vincent Scoma

Hi RECO Education, 

Thank you for reaching out and letting us know! 

When publishing the course, what settings are in place? Is the course published for Web, or is it published for Tin Can? Also, is the Exit course button not working on desktop and mobile devices? 

Let us know if this lines up with what you are seeing. If you can share your file with us, we are more than happy to take a closer look! You can privately upload the file here!

lee barry

This isn't very good, looking to switch back to Articulate but with all updates installed I am having the same issue. Exit will not work in Chrome or Firefox, but will in Edge (but who uses edge). This is not a developer issue. The trigger code used is extremely simple:

Exit course when user clicks rectangle 2.

Course tested (& exit fails) by publishing to articulate online. Exact same outcome when published to local computer: Works for Edge but not Chrome or Firefox

Caryn Carman

Hello! I added a post to a similar thread that was just created yesterday (4/23/20) but I'm going to add here as well in case it makes sense.

I did 2 updates this week (Articulate & SL) for 360 and now my "exit course" trigger is not working in the modern player, hosted on my LMS, with the course running in new window. Instead of closing the window, or informing the learner that the course is over & they can close the window, an error msg appears:  "No content". It seems to be browser independent.

I'm launching two new courses next week that currently use this trigger. Aside from pulling out the trigger, are there any fixes I can apply?

Many thanks!

Vincent Scoma

Hi Caryn,

Thank you for letting us know! 

May I ask if you could share a bit more details on this:

  • When publishing the course, which format is selected? (Publish to Web, Publish to LMS, etc.) 

In the meantime, I wanted to share a help guide that I hope will clear things up: 

Please keep us updated and let us know if you have any questions! 

Caryn Carman

Hi Vincent,

It's published to LMS - HTML only. The same exact file was published the same way prior to the last update, and the trigger seems to work there. For now, I've simply removed the trigger since the workarounds did not help and I need to go live. I'll keep watching the thread for any additional updates. 

I did receive notifications of others posting to this and related threads reporting the same thing since the latest update. 



Chelsie Colvin

Hi all,

We're experiencing a similar issue with some training that's required for a couple hundred internal employees. We've had at least 25 employees so far reporting that when they click NEXT or EXIT, the application hangs and does not record completion. We're publishing to HTML5 only, using the Classic Player in SuccessFactors LMS. This is affecting both SCORM 2004 4th ed. and SCORM 1.2 courses. Any insight or help would be great! Thanks in advance!

Leslie McKerchie

Hi Caryn,

Thanks for reaching out! I'm so sorry you're seeing an error when exiting courses that you published with the latest Storyline 360 update. We'll fix this in our next update, and here's how you can avoid it in the meantime.

1. Go to the following folder on your computer, depending on your version of Windows:

32-bit Windows
C:\Program Files\Articulate\360\Storyline\Content\scormdriver_v7

64-bit Windows
C:\Program Files (x86)\Articulate\360\Storyline\Content\scormdriver_v7

2. Open the scormdriver.js file in a text editor, such as Notepad.

3. Find "goodbye.html" and replace it with "lms/goodbye.html" (including the quotes).

4. Save and close the scormdriver.js file.

5. If you've customized the goodbye.html file, you also need to copy and paste your custom goodbye.html file into the folder from step 1 above. If you haven't customized the goodbye.html file, you can skip this step.

Then republish your course and upload it to your LMS. Let me know if that solves the problem.

Ashley Terwilliger-Pollard

Hi all,

Good news! We released an update for Storyline 360 that fixes the 404 error you recently reported.

If you already fixed your courses using the instructions from Leslie, you don’t need to republish those courses. The latest update prevents the 404 error from happening in courses that you publish from this point forward.

Let us know if you have any questions. We're happy to help!

Leslie McKerchie

Hi Diane,

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.39.22088.0 of Storyline 360. You can read all of the details here.

If you're still seeing the issue in the latest update, we would certainly want to take a closer look.