Weavara Preflight Test a package

Weavara Preflight

Why a course does not mark complete in the LMS

Most courses that stay in progress do so for one of a handful of reasons, and each shows in what the course sends to the LMS. Preflight plays the package against a stand-in LMS and names the one that applies.

Open Preflight and drop a zip Free, no account.

The usual causes

CauseWhat Preflight shows
The course never sets a statusReported nothing. Completion: never set.
The status comes after the finish callCompletion: set after the finish call, when the LMS has stopped listening.
The course never calls finishFinish: never called. Many LMSs save the session only when it is.
Nothing is saved before the tab closesSave: never called before finish.
Pass or fail with no completion status (SCORM 2004)Completion: pass or fail with no completion status. Some LMSs leave the course in progress.
A raw score with no scaled score (SCORM 2004)Score: many SCORM 2004 LMSs grade by the scaled score and show none.
Saved progress over the limitSuspend data: over the limit for the standard and edition. Many LMSs cut it off, which breaks resume.
The status goes backwards on a later visitCompletion: the last visit ended passed, this one set incomplete.
xAPI: no completed statementCompleted: not sent.
cmi5: no terminated statementTerminated: not sent. The LMS treats the session as abandoned.

Causes in the settings

The tracking option chosen when the course was published (slides viewed, a quiz result, or a trigger) decides what the course sends. Preflight shows the status the published package actually sends, so a setting that does not match what the LMS expects shows up there.

The LMS has settings of its own, such as completing a course on passed rather than on completed. Those are in the LMS, and Preflight leaves them to it.

Questions

It completes in one LMS and not in another. Why?
LMSs differ in what they accept and what they do with a missing value. Strict mode in Preflight refuses what strict LMSs refuse, so it shows where a stricter LMS would break the course.
Where do I fix it?
In the authoring tool: the publish settings or the course's triggers. Publish again and drop the new zip on Preflight to check.
Can I check the Storyline file itself?
StoryAudit reads the .story file without Storyline and shows its completion path.