Need help on connected packages

NathalieHebenst​ - Thanks! However, we do not have issue with SCORM compatibility, as all our courses are launched in 2004 4th Ed in standard packages. I think the issue here is with connected packages. Traditional/standard package has its own local SCORM exit infrastructure like, CourseExit.js, goodbye.html, scormdriver.js, etc., whereas in the Connected Package, its indexAPI.html loads in Articulate's hosted host.js and then runs the course through a hosted boot.html inside an iframe. In short, the Connected Package does not include its own exit page locally; exit is handled remotely/ dynamically by Articulate's hosted runtime and for some reason exit-return-navigation model are not interacting cleanly in SF Learning. I tried testing in SCORM cloud as well, and its the same error.