Forum Discussion
Rise: Adding Storyline360 course is not possible, stucks on processing
Hello, i would like to add a Storyline360 course in my rise course. But after selecting the course in the review360 list, it gets stuck on processing all day and night. I tried out with different browsers and even my colleaques had no succes. Does anyone else has the same problem or may help?
Thanks, Jessica
Hello JessicaRossi!
Thanks for reaching out. Happy to help!- You mentioned trying to test this out in different browsers. Could you confirm if this same behavior is happening in a brand new Rise course as well?
- Are you working on a shared or highly secure network? I'm curious if you are connected to a VP and/or Firewall enabled network that could possibly be preventing your access across your whole team. Our engineers have recommended temporarily disconnecting from them to see if there is any change to your experience.
Looking forward to hearing from you!
- JessicaRossiCommunity Member
Hello LucianaPiazza ,
Thank you for your reply.
Yes, I tried it in a new empty course and I also asked my colleagues who had the same behavior. I also did not use the VP nework.
In the meantime I realized that 2 out of 4 storyline courses could be connected. So I tried to publish the ones that didn't work with a new name and even build them as a new course in Articulate. But it didn't help. At least I solved the problem by copying and pasting the pages into the working course, deleting the old pages and publishing the course under a new name. With this workaround, I was able to connect the storyline courses in rise. However, I'm not sure what the problem is as I have the same settings in all courses.
Hello JessicaRossi,
If copying your content to a working course fixed the issue, the problem may have been file-specific. You'll want to ensure you're working locally to reduce the risk of running into issues with your project files. If you're still experiencing the problem, please share a copy of your project file here or privately by opening a support case so we can take a closer look at what's happening. We'll delete it when we're done testing!