Fixing SCORM Package Export and Import Inconsistencies
This behavior has been resolved and deployed to the production environment as of 9/18/24.
Description
We're encountering issues where Commons packets retain outdated references from the source course when they are created. This leads to mismatches and inaccuracies when the source content references are updated after the export.
When SCORM content is exported for use in Commons, it captures and locks the references from the source course in the state of reference. If these references in the source course are updated post-export, the changes are not reflected in the Commons content, causing 404 errors.
Expected Behavior
Allow for dynamic updating of references within SCONE to ensure that references are updated as soon as changes are detected in the source content.
Workaround
No workaround exists at this time.
Steps to Reproduce
No steps to reproduce exists at this time.
Additional Info
RCX-2214
Known issues indicate notable behaviors that have been escalated to the Canvas engineering team. Known issues are not a guarantee for an immediate resolution. This document is for informational purposes only and does not replace the Support process. If you are encountering the behavior outlined in this document, please ensure you have submitted a Support case (per your institution's escalation process) so Canvas Support can adequately gauge the overall customer impact and prioritize appropriately.