I have been trying to search the forums to find anything on this but have had no luck. Has anyone run into an issue before where the "would you like to resume where you left off' prompt isn't working where the issue is the Yes button just does not respond to clicks at all? We are running into that with one of our courses today and I am trying to figure out what is causing it.
Yes, only the Yes button is not working; the No option works as expected. It happens both if I publish for web and run locally or if I publish to SCORM and run on our LMS. It was first discovered in the SCORM version, I tried it locally as I was trying to troubleshoot and saw the same behavior. Have never had a course behave this way before.
It certainly sounds odd - are you able to try importing the project into a new Storyline project to see if it resolves any odd behavior? If that doesn't change anything, can you share the Storyline file with us?
Hi, wondering if you ever found a fix for this. I'm having the exact same problem. I tried re-publishing with the most recent Storyline 2 update, too.
If I hit 'Yes', nothing happens, and if I hit 'No' subsequently, it does not actually restart fresh. All the visited states are already toggled, and on the last screen, the 'Prev' button turns into a 'Submit' button. Really odd!
If I hit 'No' to begin with, however, the chapter does start fresh.
This thread is a bit older, and I don't see any additional info from Ian on this. Are you testing this in your LMS or a web server? Have you looked at testing the course at SCORM Cloud? It's an industry standard for testing LMS content.
We have this issue with courses as well. The "yes" button from resuming does not work however the "no" button works as expected. Unfortunately, it is not a consistent issue for the same course. It just appears to stop working at random for different users. Any ideas on where to look or how to fix this issue? We have tested all our courses on SCORM Cloud and usually they work fine on our LMS as well. Just every once in awhile this issue will come up.
I didn't hear back from Irene, and don't see if she submitted a support case either. Are you able to determine if the users who see this are all using the same browser or doing something else similar that could be contributing to it? What happens when you click the "yes" button- does it just freeze? What if you reload that page after clicking yes?
Hi, any update about this? Im having the same issue and i did everything to fix it but still not working. :( Yes button is not working upon resume prompt.
Have you resolved this issue wayback? Just wanted to ask if the learners are all using the same browser? I have the same issue now and I cant seem to get an answer. Thanks.
I'm not seeing any further information from the users above. Hopefully they are still subscribed and will be able to chime back in. If not, you are welcome to reach out to them directly via the 'Contact Me' option on the user profile if needed.
Are you able to replicate you issue in SCORM Cloud? Any consistency in testing/replication that we could take a look at?
You are welcome to share your .story file if you need us to take a look.
I'm not seeing any further information from the users above. Hopefully they are still subscribed and will be able to chime back in. If not, you are welcome to reach out to them directly via the 'Contact Me' option on the user profile if needed.
Are you able to replicate you issue in SCORM Cloud? Any consistency in testing/replication that we could take a look at?
You are welcome to share your .story file if you need us to take a look.
Hi Leslie,
Given this was two years ago I honestly do not know what our end result was. It was inconsistent and we have not seen it in a course since. I will however be retesting this item this week in our baseline course template as we are going through an effort to retest any items like this that might still be open that we reported. I'm going through my old post history today and finding anything that might not have been resolved as part of that effort. I'll respond here with any new info I come across.
Still no solution for this? I am trying to fix it for the past 4 weeks but still the same... I am working with Bret but no update yet. Its not an HTML issue... not a suspend data limit issue as well since its working in some attempts. Ive tried slimming the slides down but sill resume doesnt work... I am getting frustrated... :(
Hi Ashley! Thanks for mentioning that you are working with Bret (00895773). As you can see here, I have not heard back from any of these users to offer any further assistance. Hopefully they are still subscribed and able to pop in with an update. In the meantime, I would continue working with Bret :) Thanks so much.
I was wondering if anyone found a cause and solution to this issue. I am experiencing the same with a course, and I have tried everything I can think of.
I have tweaked the resume settings in Articulate with no luck, as well as looking into my LMS. The issue, I believe, is in the Articulate file content, because publishing to Web or CD yields the same result as publishing to LMS.
I have tried importing to a new story file, slimming down the slides, and adjusting the reporting and tracking settings.
Any possible insight into this would be much appreciated.
I took a look and it seems that Ashley and Bret are still working through this issue. If you'd also like our team to take a look, can you share a copy of your .story file with us here?
I found a solution on my end that I hope can benefit anyone else who experiences this issue. For the record, I was publishing my Articulate Storyline 2 file to LMS, uploading it, and testing it. In the LMS, the Click Yes to Continue button was not functional. Nothing happened upon clicking, so that you were forced to click No and start the course from the beginning.
In the course, there was a specific slide that was causing the issue. I discovered this by making a copy of my .story file for test purposes, and systematically removing scenes from it until the course acted as desired within the LMS.
Once I identified the scene that "broke" the course, I repeatedly deleted slides and published the course until I identified the problem slide.
It turns out that Articulate simply did not like the text I used on that slide, despite there being no odd characters and it being in the same font as the rest. I deleted and retyped out all text on the slide (this one had no Notes text; I would suggest retyping that as well).
After all that, the published course could be resumed utilizing the Yes to Resume button.
This is not the first time Storyline has acted up in response to seemingly normal text for me, so this issue is not surprising. I wish anyone who has this issue luck, especially if your course is as big as the one I'm working on and therefore as time-consuming to fix.
We were also thinking that 1 slide is causing it but we dont know which slide is it since It was a big course and a lot of branching.... :( Can you share what is the step you did? I still have my issue with that and it hasn't been resolved on my end.. :(
Can you share that one slide in question? It's definitely something I'd want to take a look at and we could help determine if there was something specific on that slide or if it was an overall issue of corruption within the slide. I haven't seen that impact a courses Resume behavior, but unfortunately there is a first time for everything.
If you can't share here in ELH, you can upload to me here and I can take a look.
As I mentioned above, I had to remove scenes and slides from the course, publishing after each time I deleted some, to find the problem slide.
Here's what to do:
1. Use the Save As function to make a test copy of your file. So, CourseName_Test.story can be the one you tweak.
2. Divide and conquer. Delete half the scenes in your course.
3. Publish the course and test it. If the Yes to Resume button still does not function, try publishing the other half of your course (the one you previously deleted).
4. If it works now, there's a slide somewhere in the deleted bunch that's messing things up. Try inserting scenes back into your test document. You can copy these out of the original story file and paste into the test file. Insert a few scenes at a time, then republish.
5. Using this process, you will have to narrow down the number of scenes copied in until you find the one scene that causes the Yes to Resume button to malfunction. Then, you will have to rinse and repeat the delete and publish process with the individual slides in the culprit scene.
6. In the end, you hopefully find ONE slide in the entire course that causes the Yes button to malfunction when you publish it. From there, look at the text on that slide and in the Notes for that slide. Any odd characters could break it; for example, I once had a course keep crashing because I was using subscripted numbers in the Notes text. If nothing immediately stands out, try deleting and retyping all text on that slide.
7. Republish and test. If you can publish the course now and the Yes to Resume button works, you should then replace the text on the problem slide in the ORIGINAL file. If it still doesn't work, you may have more than one slide in the course that is corrupted. Continue the above process until you have tested EVERY SCENE for a bad slide.
If this does not solve it, your issue may be caused by something else. In which case, I wish you the best of luck!
Thanks Shannon for sharing the steps - I know what a cumbersome process that could be and it sounds like you were able to isolate it to the notes and some subscripts on that slide? If you're still looking to figure out what may have been the cause - I'm happy to give it a look too. With odd behaviors and corruption, it may not be something we could spot but always willing to put another pair of eyes on it just in case!
Was there any update to this issue as I think we're experiencing the same thing. I've tested the file on our LMS and on SCORM Cloud and it happens on both so pretty sure the issue is with the Storyline file. But can't see anything in the file that is set incorrectly and I'd like to avoid Shannon's issue identification process if possible!
Hello Robert - As mentioned above, Ashley worked with our support team and her issue was able to be replicated with her file. We are still working on this issue. That being said, it sounds like you are able to consistently reproduce the issue you are having, so I would encourage you to share your .story file as well so that we can take a look. That certainly assists in diagnosing. If you cannot share here, please be sure to share privately here.
27 Replies
Hi Ian,
It's only the Yes button that doesn't work? Where are you testing the published content? You'll want to make sure you're testing within the intended environment as testing it locally could cause odd or unexpected behavior.
Yes, only the Yes button is not working; the No option works as expected. It happens both if I publish for web and run locally or if I publish to SCORM and run on our LMS. It was first discovered in the SCORM version, I tried it locally as I was trying to troubleshoot and saw the same behavior. Have never had a course behave this way before.
Hi Ian,
It certainly sounds odd - are you able to try importing the project into a new Storyline project to see if it resolves any odd behavior? If that doesn't change anything, can you share the Storyline file with us?
Hi, wondering if you ever found a fix for this. I'm having the exact same problem. I tried re-publishing with the most recent Storyline 2 update, too.
If I hit 'Yes', nothing happens, and if I hit 'No' subsequently, it does not actually restart fresh. All the visited states are already toggled, and on the last screen, the 'Prev' button turns into a 'Submit' button. Really odd!
If I hit 'No' to begin with, however, the chapter does start fresh.
Any advice?
Hi Irene,
This thread is a bit older, and I don't see any additional info from Ian on this. Are you testing this in your LMS or a web server? Have you looked at testing the course at SCORM Cloud? It's an industry standard for testing LMS content.
Hi There,
We have this issue with courses as well. The "yes" button from resuming does not work however the "no" button works as expected. Unfortunately, it is not a consistent issue for the same course. It just appears to stop working at random for different users. Any ideas on where to look or how to fix this issue? We have tested all our courses on SCORM Cloud and usually they work fine on our LMS as well. Just every once in awhile this issue will come up.
Thank you!
Karoline
Hi Karoline,
I didn't hear back from Irene, and don't see if she submitted a support case either. Are you able to determine if the users who see this are all using the same browser or doing something else similar that could be contributing to it? What happens when you click the "yes" button- does it just freeze? What if you reload that page after clicking yes?
Hi, any update about this? Im having the same issue and i did everything to fix it but still not working. :( Yes button is not working upon resume prompt.
Hi Karoline,
Have you resolved this issue wayback? Just wanted to ask if the learners are all using the same browser? I have the same issue now and I cant seem to get an answer. Thanks.
Hi Ashley!
I'm not seeing any further information from the users above. Hopefully they are still subscribed and will be able to chime back in. If not, you are welcome to reach out to them directly via the 'Contact Me' option on the user profile if needed.
Are you able to replicate you issue in SCORM Cloud? Any consistency in testing/replication that we could take a look at?
You are welcome to share your .story file if you need us to take a look.
Hi Leslie,
Given this was two years ago I honestly do not know what our end result was. It was inconsistent and we have not seen it in a course since. I will however be retesting this item this week in our baseline course template as we are going through an effort to retest any items like this that might still be open that we reported. I'm going through my old post history today and finding anything that might not have been resolved as part of that effort. I'll respond here with any new info I come across.
I understand Ian. Thanks for popping in with an update. I've seen some steel-trap memories in the forums for sure :)
Still no solution for this? I am trying to fix it for the past 4 weeks but still the same... I am working with Bret but no update yet. Its not an HTML issue... not a suspend data limit issue as well since its working in some attempts. Ive tried slimming the slides down but sill resume doesnt work... I am getting frustrated... :(
Hi Ashley! Thanks for mentioning that you are working with Bret (00895773). As you can see here, I have not heard back from any of these users to offer any further assistance. Hopefully they are still subscribed and able to pop in with an update. In the meantime, I would continue working with Bret :) Thanks so much.
I'm staying with you on this until we figure it out, Ashley.
Thank you for being so patient.
Hi all,
I was wondering if anyone found a cause and solution to this issue. I am experiencing the same with a course, and I have tried everything I can think of.
I have tweaked the resume settings in Articulate with no luck, as well as looking into my LMS. The issue, I believe, is in the Articulate file content, because publishing to Web or CD yields the same result as publishing to LMS.
I have tried importing to a new story file, slimming down the slides, and adjusting the reporting and tracking settings.
Any possible insight into this would be much appreciated.
Hi Shannon,
I took a look and it seems that Ashley and Bret are still working through this issue. If you'd also like our team to take a look, can you share a copy of your .story file with us here?
Hi all,
I found a solution on my end that I hope can benefit anyone else who experiences this issue. For the record, I was publishing my Articulate Storyline 2 file to LMS, uploading it, and testing it. In the LMS, the Click Yes to Continue button was not functional. Nothing happened upon clicking, so that you were forced to click No and start the course from the beginning.
In the course, there was a specific slide that was causing the issue. I discovered this by making a copy of my .story file for test purposes, and systematically removing scenes from it until the course acted as desired within the LMS.
Once I identified the scene that "broke" the course, I repeatedly deleted slides and published the course until I identified the problem slide.
It turns out that Articulate simply did not like the text I used on that slide, despite there being no odd characters and it being in the same font as the rest. I deleted and retyped out all text on the slide (this one had no Notes text; I would suggest retyping that as well).
After all that, the published course could be resumed utilizing the Yes to Resume button.
This is not the first time Storyline has acted up in response to seemingly normal text for me, so this issue is not surprising. I wish anyone who has this issue luck, especially if your course is as big as the one I'm working on and therefore as time-consuming to fix.
Cheers!
Hi Shannon,
We were also thinking that 1 slide is causing it but we dont know which slide is it since It was a big course and a lot of branching.... :( Can you share what is the step you did? I still have my issue with that and it hasn't been resolved on my end.. :(
Hi Shannon,
Can you share that one slide in question? It's definitely something I'd want to take a look at and we could help determine if there was something specific on that slide or if it was an overall issue of corruption within the slide. I haven't seen that impact a courses Resume behavior, but unfortunately there is a first time for everything.
If you can't share here in ELH, you can upload to me here and I can take a look.
Hi Ashley,
As I mentioned above, I had to remove scenes and slides from the course, publishing after each time I deleted some, to find the problem slide.
Here's what to do:
1. Use the Save As function to make a test copy of your file. So, CourseName_Test.story can be the one you tweak.
2. Divide and conquer. Delete half the scenes in your course.
3. Publish the course and test it. If the Yes to Resume button still does not function, try publishing the other half of your course (the one you previously deleted).
4. If it works now, there's a slide somewhere in the deleted bunch that's messing things up. Try inserting scenes back into your test document. You can copy these out of the original story file and paste into the test file. Insert a few scenes at a time, then republish.
5. Using this process, you will have to narrow down the number of scenes copied in until you find the one scene that causes the Yes to Resume button to malfunction. Then, you will have to rinse and repeat the delete and publish process with the individual slides in the culprit scene.
6. In the end, you hopefully find ONE slide in the entire course that causes the Yes button to malfunction when you publish it. From there, look at the text on that slide and in the Notes for that slide. Any odd characters could break it; for example, I once had a course keep crashing because I was using subscripted numbers in the Notes text. If nothing immediately stands out, try deleting and retyping all text on that slide.
7. Republish and test. If you can publish the course now and the Yes to Resume button works, you should then replace the text on the problem slide in the ORIGINAL file. If it still doesn't work, you may have more than one slide in the course that is corrupted. Continue the above process until you have tested EVERY SCENE for a bad slide.
If this does not solve it, your issue may be caused by something else. In which case, I wish you the best of luck!
Hi Ashley,
I will have to check to make sure I am allowed to share the file with you. I will definitely have to share it privately, if I can share it at all.
Thanks for the help!
Thanks Shannon for sharing the steps - I know what a cumbersome process that could be and it sounds like you were able to isolate it to the notes and some subscripts on that slide? If you're still looking to figure out what may have been the cause - I'm happy to give it a look too. With odd behaviors and corruption, it may not be something we could spot but always willing to put another pair of eyes on it just in case!
Was there any update to this issue as I think we're experiencing the same thing. I've tested the file on our LMS and on SCORM Cloud and it happens on both so pretty sure the issue is with the Storyline file. But can't see anything in the file that is set incorrectly and I'd like to avoid Shannon's issue identification process if possible!
Hello Robert - As mentioned above, Ashley worked with our support team and her issue was able to be replicated with her file. We are still working on this issue. That being said, it sounds like you are able to consistently reproduce the issue you are having, so I would encourage you to share your .story file as well so that we can take a look. That certainly assists in diagnosing. If you cannot share here, please be sure to share privately here.
This discussion is closed. You can start a new discussion or contact Articulate Support.