I have been working on this project in Storyline 360 for week and each I have been publishing it regularly to see how its coming out. I have not had any issues until today. This time when I click view or open the file is not opening. It starts to load and goes on and on. The same happens if try opening the saved story_html5. My saved old published html files are opening in seconds. Any ideas how I can fix this? The file is attached.
Hi there, Naison. It sounds like you may be trying to view the file locally after publishing. It's possible that a browser setting may have changed that is preventing local playback. First, to make sure you file is playing back properly, try publishing to Articulate 360. You can then launch the course in Articulate Review and test your build.
To troubleshoot why it isn't launching locally, let me grab some details:
What is the browser that is used to open the course when you click to view it? Does it work in any other browser?
What build of Storyline are you using? Go to Help > About Storyline.
Feel free to try to attach your file again for testing! Use the Add Attachment button in the discussion reply. You can also send it to me privately.
Just to give an update: We identified the issue with Naison's file. It was a question bank that accidentally acquired too many slides. Once it was cleaned up, everything functioned as normal!
Keith, if you still need help, feel free to let me know!
I have tried Internet Explorer, Google Chrome, even Microsoft Edge! LOL
Like the gentleman above, the file just keeps spinning.
There are no quiz questions or results slides. There is audio however.
I played around with the Browser settings in the Player but none of it seems to make a difference. (Launch player in a new window, Display Browser at current browser size,etc.)
I have tried several times to republish but I keep getting the same result.
Hi, Sandra. Sorry to hear you're at this roadblock!
We're happy to help you sort this, and have a few key questions to start:
Did you publish the course for Web, LMS, or something else?
Would you mind sharing your .story file so I can try to replicate the behavior? You can share it publicly here, or send it to me privately by using this upload link. I'll delete it when we solve this puzzle!
Hi Joseph. Thanks for sharing your file so we can dig in!
Here's a recap of my testing:
I imported the Engage interaction into Storyline 3 Update 9. From there, I successfully published the slide for Web and hosted it on Tempshare. You can view the course through this link ⤶
Then, I viewed the output in Firefox Version 75 where the content looks great. You can check out the behavior through this link ⤶
Walk me through what you're seeing. Do any errors appear? Also, how does the course look when you test my link?
Hi everyone, I'm having the same trouble as the original poster of this thread. I'm having trouble opening a published file (done with Storyline 3) even though I can do that with other files I worked with. I tried opening it locally, and then after uploading the content to Azure storage as well. Could someone please help? Thank you!
If importing your slides to a new project file and republishing your course doesn't work, would you be willing to upload a copy of your project file here or in private by opening a support case so we can take a closer look at what's happening? We'll delete it as soon as we're done troubleshooting.
Thanks a lot for reaching out, I tried importing the slides into a blank file and now it works! Thanks a lot for your speedy and kind suggestion, much appreciated!
I have been having the same issue as above. I create a whole course in storyline and then wanted to export modules individually and so was copying slides into a new project and when this was uploaded into my LMS each module was getting stuck each time on the second slide. The only way to fix this seemed to be if I went back to the original project and then deleted all the slides not related to the specific module I wanted to upload and then saved this as a new project. I'm wondering if maybe there is some kind of bug with copied slides?
Copying/importing content across projects shouldn't be an issue as long as you're working locally when doing so. If your course is getting stuck on one of the slides, please share a copy of your project file here or in private by opening a support case for testing. We'll delete it afterwards!
15 Replies
There is no file attached.
Hi there, Naison. It sounds like you may be trying to view the file locally after publishing. It's possible that a browser setting may have changed that is preventing local playback. First, to make sure you file is playing back properly, try publishing to Articulate 360. You can then launch the course in Articulate Review and test your build.
To troubleshoot why it isn't launching locally, let me grab some details:
Here's more information on viewing your project after publishing.
Hi,
Do you work for customer support at Articulate? I seem to be having the same problem as the guy above...
Thanks
Hi there, Keith! I'm happy to help you. Can you let me know the following:
You can always reach our team here as well!
Just to give an update: We identified the issue with Naison's file. It was a question bank that accidentally acquired too many slides. Once it was cleaned up, everything functioned as normal!
Keith, if you still need help, feel free to let me know!
Me Too!
I have a Storyline 2 HTML file that won't open.
I have tried Internet Explorer, Google Chrome, even Microsoft Edge! LOL
Like the gentleman above, the file just keeps spinning.
There are no quiz questions or results slides. There is audio however.
I played around with the Browser settings in the Player but none of it seems to make a difference. (Launch player in a new window, Display Browser at current browser size,etc.)
I have tried several times to republish but I keep getting the same result.
Don't know what to try next! Any ideas?
Hi, Sandra. Sorry to hear you're at this roadblock!
We're happy to help you sort this, and have a few key questions to start:
I'm having same issues so i do not want to waste time. I use Storeyline 3 with Mozilla Firefox
Hi Joseph. Thanks for sharing your file so we can dig in!
Here's a recap of my testing:
Walk me through what you're seeing. Do any errors appear? Also, how does the course look when you test my link?
Looks great, thank you.
Hi everyone, I'm having the same trouble as the original poster of this thread. I'm having trouble opening a published file (done with Storyline 3) even though I can do that with other files I worked with. I tried opening it locally, and then after uploading the content to Azure storage as well. Could someone please help? Thank you!
Hello Chi,
Thanks for reaching out!
If importing your slides to a new project file and republishing your course doesn't work, would you be willing to upload a copy of your project file here or in private by opening a support case so we can take a closer look at what's happening? We'll delete it as soon as we're done troubleshooting.
Looking forward to hearing from you!
Hi Joe,
Thanks a lot for reaching out, I tried importing the slides into a blank file and now it works! Thanks a lot for your speedy and kind suggestion, much appreciated!
A very nice weekend to you!
Best, Chi Le.
I have been having the same issue as above. I create a whole course in storyline and then wanted to export modules individually and so was copying slides into a new project and when this was uploaded into my LMS each module was getting stuck each time on the second slide. The only way to fix this seemed to be if I went back to the original project and then deleted all the slides not related to the specific module I wanted to upload and then saved this as a new project. I'm wondering if maybe there is some kind of bug with copied slides?
Hi Grace,
Happy to check this for you!
Copying/importing content across projects shouldn't be an issue as long as you're working locally when doing so. If your course is getting stuck on one of the slides, please share a copy of your project file here or in private by opening a support case for testing. We'll delete it afterwards!