Forum Discussion
Error message when creating a review link.
I have been trying all morning to create a review link in Storyline. Hasn't been an issue in the past. I'm getting an error message that states "Something went wrong". I've tried doing a save as, publishing from my desk top and from my shared drive. I continue to get that message. Can anyone provide assistance as to what might be happening? TIA
Hi PatriciaCharles!
Sorry to hear you're having trouble publishing to Review 360!
Does this behavior occur with all .story files you attempt to publish, or just one in particular?
Since signing in and out of the Articulate 360 desktop app didn't work, please follow the steps outlined in this article. This process will remove all Articulate 360 files and registry keys, allowing us to start fresh. However, if the issue persists, please connect with our team through a support case.
They'd be happy to continue troubleshooting with you!
I had the same issue and the steps worked for me, I additionally updated Storyline too
Having the same issue/error message
Hi BeckyNield!
Sorry to hear you're also having issues publishing to Review 360!
As others have shared, signing out of the Articulate 360 desktop app completely, then signing back in, has helped to correct this behavior. If that doesn't do the trick, and you've confirmed you are working locally, please connect with our support engineers through a support case.
They'd be happy to assist further!
Same problem here. I have tried publishing multiple SL files to Review and keep getting the same error message. I have tried renaming, changing saved locations, creating new file, etc.
A coworker and I are having the same issue. Started this morning.
Hi Patricia,
You might try this:
- Launch the Articulate 360 program on your computer. (Not Storyline)
- Sign out.
- Sign back in
- Go back into Storyline and attempt to republish.
This webpage on Diagnostics might help, too.
This worked. Pull up the Articulate 360 program, sign out, sign back in from that area.
This fixed my problem too. Thanks!
Thank you for your response. I did as you suggested and still get the same error message. This just started today.
