slow-api-discoveryThe course took seconds to find the LMS API, which usually means it was retrying after failures.
A pause on launch before anything happens, sometimes several seconds of blank frame. In the worst case the course gives up and runs untracked, which then presents as a course that never initialised.
More than two seconds between a SCO's first API activity and its Initialize call.
A course finds the LMS by walking up the window hierarchy looking for an API object. When that fails it typically retries on a timer. The delay is the retry loop, so it is a symptom of a discovery problem rather than a problem in itself — and the same conditions that make it slow here can make it fail entirely elsewhere.
Check how deeply the course is nested in frames and whether anything cross-origin sits between it and the LMS window, which blocks the search outright. Bound the search: a fixed number of levels and a fixed number of retries, then a visible failure. A course that fails loudly is far easier to diagnose than one that runs untracked.
On a slow connection this can appear without anything being wrong. Treat it as worth a look, not as a defect.
Open a package in SCORM Lab to see whether this applies to yours. It runs in your browser, and nothing is uploaded unless you choose to share it.
Stuck on this one, or seeing it only in a particular LMS? That is usually a short conversation — scormspecialist.co.uk.