Rise 360 Connected Packages, LMS API error when switching publishing standards

Heads-up if you’re testing Rise 360 Connected Packages in both SCORM 1.2 and SCORM 2004. I found that publishing the same Rise course under a different SCORM standard can cause an existing LMS upload to stop launching.

In SCORM Cloud, my original Connected 2004 package launched successfully. I went back to the same Rise course, published it as Connected 1.2, and downloaded the ZIP. Before I uploaded the new ZIP anywhere, the existing 2004 course started showing “Unable to acquire LMS API.” The network capture showed that Articulate was now serving a 1.2 configuration to that launch. I also reproduced the reverse, where an existing 1.2 upload received a 2004 configuration and failed.

Workaround for testing: Create a separate Rise course copy for each SCORM standard. Keep one copy on 1.2 and the other on 2004. Fresh exports from separate copies launched successfully in my SCORM Cloud tests.

If an existing course already fails: In a test environment, try publishing the same Rise course again using the original upload’s SCORM standard, then relaunch that existing upload. I’ve confirmed that republishing changes the hosted target, and I’ve asked Articulate Support to confirm the recovery steps for live courses with learner history. If both standards are already deployed from the same Rise course, coordinate the change first, since switching back could affect the other upload.

I’ve shared the reproduction and captures with Articulate Support. If you’ve seen this on your end, I’d be interested to hear if anyone has encountered this!