When uploading a SCORM package from Cognota's design tool into Cornerstone, you may see warning messages during the import process.
These warnings can look alarming, but do not impact the learner experience or the integration between Cognota and Cornerstone. The SCORM package should still function as expected once published.
Why this happens
SCORM import warnings in Cornerstone are typically generated by how Cornerstone validates incoming packages — not by an error in the course itself. Common triggers include:
Metadata fields that Cornerstone flags as non-standard but still accepts
Minor structural differences between SCORM versions (1.2 vs 2004) and Cornerstone's expected format
Warning-level validation messages that Cornerstone surfaces even for fully functional packages
These are warnings, not errors. A warning means Cornerstone has flagged something for review — it does not mean the upload failed or the course is broken.
What to do
Proceed with publishing. The SCORM package should launch and track as expected in Cornerstone despite the warnings.
After publishing, verify the course by:
Launching it as a learner in your Cornerstone environment
Confirming it loads and progresses correctly
Checking that completion and score data are being recorded