It seems like you're encountering issues with your course in Storyline 360 not correctly reporting user answers back to your LMS, particularly when using the Question Bank or when the course bounces to the Results slide based on certain answers.
Here are some potential troubleshooting steps and considerations:
Check LMS Compatibility: Verify if the version of SCORM you're publishing (SCORM 2004 v3) is fully compatible with your LMS (Cornerstone). Sometimes, certain versions or configurations might not fully support specific interactions or data reporting. It might be worth checking with Cornerstone's support or documentation for any known compatibility issues.
Review Reporting Settings: Within Storyline 360, check the Reporting and Tracking settings when publishing the course. Ensure that reporting of user answers is enabled and configured properly. Specifically, make sure that the reporting of interaction data is set up correctly for your question slides.
Interaction ID and Reporting: Each question slide should have a unique interaction ID for the LMS to track and report user answers. Ensure that the interaction IDs for your questions are correctly set up in Storyline.
Testing in SCORM Cloud: Use SCORM Cloud (a testing platform for SCORM packages) to test your published course. This allows you to isolate whether the issue is related to your LMS (Cornerstone) or something in the course content itself.
Review Triggers and Navigation: Ensure that there are no conflicting triggers or navigation settings that might interfere with the reporting of user answers to the LMS. For instance, verify that when users navigate to the Results slide, it doesn't interfere with data tracking.
Engage Articulate Support: If the issue persists after trying these steps, consider reaching out to Articulate Support. They might have encountered similar issues and could provide specific guidance or troubleshooting steps.
Regarding the advice to place questions on individual slides rather than using the Question Bank, while this method might sometimes alleviate certain issues, it shouldn't inherently prevent user answers from being reported back to the LMS if the reporting settings and configurations are correct.
Investigating these areas should help identify where the issue might be occurring and help resolve the problem with reporting user answers back to your LMS accurately.
