BUG: Completion Certificate Issued Prematurely
A known issue can cause a completion certificate for a practice unit to be sent as soon as a learner finishes the induction sequence, before they've actually completed that unit.
⚠️ Known issue: We're aware of this bug and a fix is in progress.
What's happening
When a learner selects their avatar and completes the induction sequence, the system incorrectly marks the practice unit that follows it as complete, and issues that unit's completion certificate — even though the learner hasn't actually done the unit.
This is not just a certificate display issue: the unit is recorded as complete in Bodyswaps, which will show up in completion reporting and any downstream tracking (e.g. LMS syncs, compliance records), and gives the learner no in-app prompt to go back and actually complete it.
Workaround: Skip the onboarding sequence
- Have the learner select their avatar as usual.
- Instead of completing the induction sequence, select "Skip this activity."
- This avoids triggering the premature completion and certificate for the unit ahead.
⚠️ Trade-off: If a learner completes the full induction sequence instead of skipping it, the unit will be marked complete early, and they may later get a second completion certificate when they genuinely complete the unit. There is currently no way to prevent or suppress the premature completion after the fact.
How to spot affected learners
Check the learner's activity log to tell whether a completion was genuinely earned:
- Navigate to the learner's profile or the class activity log.
- Find the assignment in question.
- Check the time spent on it.
- If the learner was only in the assignment for one to two minutes, that's a strong sign the completion came from this bug rather than real completion of the unit.
Fix status
Our team is working on a fix for this issue. This article will be updated once it's resolved.