Forum Discussion
Storyline not publishing to Review
Hello all,
My team and I have been trying to publish some storyline files to review today, but we keep getting an error. I didn't see anything on the Articulate Status page, so I thought I would check in here to see if anyone else is having this issue today?
Any help would be greatly appreciated! Thanks so much!
Hi Everyone!
I'm sorry to hear you've been impacted by this hiccup!
I see that some of you have connected with our team, privately through support cases. Smart move!
We noticed the same issue on our end. I'm happy to share our team has put a fix in place, and we can confirm that all systems are now operational. Please don't hesitate to reach out if you run into any trouble!
For your reference, you can also see real-time status updates, here: https://www.articulatestatus.com
18 Replies
We're seeing this as well. Last thread showed it was an Articulate system issue. Hopefully they'll fix it soon.
I think Articulate must be having issues on their side. I had published some files to review 360 earlier today, but they won't process to RISE when I'm trying to embed them. And I keep getting an error every time I add a new block to RISE.
I am getting the something very similar trying to publish something in Rise. It happens both trying to publish to the Review tool and to LMS. It says Something went wrong. There was an error publishing your course. Please try again.
We are experiencing the same issue. Unable to publish SCORM files from RISE.
I'm having trouble uploading images to Rise. It tells me the file isn't in the right format.
I experienced the same thing just now. Hopefully they'll fix it soon :)
I am having the same issue.
Same here. None of my team members are able to publish
I submitted a case and they emailed me back saying to clear my browser cache and try again. I just tried again (without clearing my browser's cache) and it seems to work.
Thank you!!!! It's working now for me as well.
It's back for me as well, without clearing my cache. Clearly this was not a cache issue Articulate.
