Skip to main content

Platform proof

Dated, public evidence for Allure Connect: live status, hosted Storyline launches, session progress mapping, and the xAPI LRS self-test.

This page lists dated platform evidence. It does not name customers or publish workspace-specific package ids, session ids, launch URLs, or webhook receivers.

Live system status

Continuous

Self-reported operational status and uptime samples for the API, dashboard, and data backend. Observations, not a contractual SLA.

Open status

Hosted Storyline launches

2026-08-27

When a SCORM package entry is launcher.html and sibling index_lms.html is present, the hosted player and content proxy serve the SCO so a blocked window.open does not prevent the course from starting.

Open changelog 2026.8.2Open dated JSON

Session progress_measure mapping

2026-08-27

Incomplete sessions map SCORM 2004 cmi.progress_measure onto progress_percent (0–99). GET and PUT /api/v1/sessions/{sessionId} also return progress as an alias. Completed, passed, and failed read as 100.

Open session docsOpen dated JSON

xAPI 2.0 LRS self-test

2026-06-06

A dated local-build run of the Allure Connect LRS passed 1,435 / 1,435 ADL suite checks. Conformant on that artifact — not IEEE or ADL certification, and not a production-endpoint rerun.

Open xAPI LRS pageOpen dated JSON

Release notes on this hub (2026.8.2)

Changed · 2026-08-27

Hosted Storyline packages whose SCORM entry is launcher.html now load sibling index_lms.html when that file is present. GET /api/v1/content/{…path} serves the SCO when a hosted request still names launcher.html, and falls back to launcher.html if the sibling is missing, so a blocked window.open no longer prevents the course from starting.

Changed · 2026-08-27

Incomplete session progress now maps SCORM 2004 cmi.progress_measure onto progress_percent (0–99 while incomplete). GET and PUT /api/v1/sessions/{sessionId} return the documented progress alias alongside progress_percent.

Not claimed here

  • IEEE or ADL SCORM certification
  • Incomplete-session progress webhooks (session webhooks remain terminal-only)
  • Production-endpoint xAPI 2.0 rerun
  • Workspace-specific package, session, or launch URLs

Workspace-specific launch URLs stay in private tickets and API responses. Retest still uses the tokenized launch_url from POST /api/v1/packages/{id}/launch.