Articulate Rise courses not always marked as completed (xAPI)

Hi Dominik,

Based on the behavior described, this appears to be related to the xAPI completion statement not consistently reaching Docebo rather than an issue with the Rise package itself.

Unlike SCORM, xAPI relies on the course generating the completion statement and successfully sending it to the LMS/LRS:

Rise Course → xAPI Statement → Docebo LRS → Completion Status Updated

If the final completion statement is not generated or not received by Docebo, the course will remain incomplete even if the learner reaches the end or passes the quiz.

Since the same packages work in SCORM Cloud and with test users, I would recommend comparing affected user sessions and checking:

• Browser/security settings that may block xAPI requests.
• Network restrictions, VPN, or extensions affecting communication.
• Whether the learner remains on the final completion screen briefly before closing the course.
• Browser developer logs to confirm whether the final xAPI completion statement is generated and successfully sent.

The key validation point is to determine whether the issue occurs at the content level (statement not generated) or during communication/processing between Rise and Docebo.

Hi ​@Dominik ,

Since you mentioned this happens with actual users who might spend more time in a course compared to quick admin test runs, another critical factor to check is Docebo session timeouts.

In Docebo, active user sessions automatically expire after a set duration of inactivity or maximum session length (typically between 1 to 3 hours, depending on your platform's Advanced Settings under Session Timeout).

When a learner leaves the course open for an extended period, the underlying LMS session can silently expire in the background. Rise continues to run locally in the browser interface, but when the learner finally completes the course or passes the quiz, the browser attempts to post the final xAPI completion statement back to Docebo. Because the session cookie/token has expired, Docebo silently rejects the incoming xAPI payload, leaving the user's status as incomplete.

This exact behavior explains why:

• Admin/Test accounts work: Admins usually click through the course quickly to verify tracking, staying well within the active session window.

• Logging in as the user reproduces it: If you reproduce it while mimicking their exact pattern or after a prolonged idle state, the session drops.

• SCORM Cloud didn't show it: SCORM Cloud doesn't enforce the same session timeout rules or domain/token authentication checks as a live production LMS.

A few practical steps to verify and mitigate this:

1. Check Session Settings: Go to Admin Menu > Advanced Settings > Options tab and review your session expiration timeout values.

2. Review User Behavior: Check the total elapsed time recorded for affected users in Docebo custom reports. If their session duration spans several hours before the attempt ends, a timeout is almost certainly the culprit.

3. Inspect Network Activity: Next time you reproduce this on an affected user account, open the browser's Developer Tools (F12) -> Network tab, filter by xAPI or LRS, and complete the course. Look for 401 Unauthorized or 403 Forbidden HTTP response codes when the final statement fires.

In organizations I've worked with that rely heavily on xAPI and longer learning modules, we've often had to balance security settings by adjusting session keep-alive intervals or adding clear learner guidance to avoid pausing content mid-stream across lunch breaks or meetings.

Hope this helps narrow down the hunt!