Skip to main content

A SCORM package was rejected

Understand why a SCORM or H5P zip fails at upload and how to fix it: re-export, recreate the archive, or check the size limit.

Written by Romain Morvant

A SCORM zip can fail before Raison reads any lesson. This page explains the messages you may see and how to fix each one. For what a successful import looks like, see Import a SCORM package.

Messages at upload

  • If Raison does not recognize the archive, the zip is not a SCORM or H5P package. Export it again from your authoring tool as a SCORM package.

  • If the archive cannot be read, it is damaged. Recreate it.

  • If the archive is too large, check the ZIP row in Supported file formats and size limits.

  • If the format is unsupported, the picker did not accept that file as SCORM or H5P.

Create collection page showing an invalid SCORM zip marked Upload failed, with Retry and Remove controls

After the package opens

You still choose which items to add, or take them all. If you confirm with nothing selected, nothing is imported. Processing errors after that work the same as for any other resource; see Understanding a resource's sync status.

H5P packages

H5P arrives as a zip too. An H5P file shown as an unrecognized archive was not packed as H5P or SCORM.

Related

Need help? Write to [email protected].

Did this answer your question?