Forum Discussion
Multiple attempts Rise
I created a course with a quiz that allows 3 attempts to achieve a 100% score.
However, tracking isn’t working properly in CMI5 via SCORM Cloud.
If I understand correctly, CMI5 only allows one status per session.
So, if the user fails their first attempt, that result will be the one shown in SCORM Cloud, even if they pass on a later attempt.
I had the same problem in Storyline earlier but managed to solve it. What I did was move when the result was submitted. I had a layer for each attempt. If you failed the first time, you were shown a layer that did not submit the result. If you failed a second time, you ended up on one that did submit the result. I reused the same “Passed” layer throughout, so it would always submit the final result.
Does anyone know a workaround to make this work in Rise?
Should Rise delay when it submits the result to the LMS to avoid multiple results clashing, or only send a failed status when it is the final attempt?
6 Replies
Hi CapperTheRose!
Happy to help!
The cmi5 publishing standard allows one 'completion' and one 'success' status per launch session. Each launch can send its own status, and the LMS is expected to record the final status based on the most recent or the highest score.
Using a sample Rise 360 course with a Quiz question allowing the learner three attempts, I also tested with SCORM Cloud. After failing my first attempt, and passing my second, SCORM Cloud reported my status accurately (complete/passed).
However, my SCORM Cloud testing was conducted all within a single launch session. Do you mind clarifying the exact steps you took, when testing in SCORM Cloud? If you failed the first attempt, then closed the session, it is expected for the LMS to mark the Learner as incomplete/failed. Alternatively, if your tests were all contained to a single SCORM Cloud session, yet the most recent (passed) attempt is not being marked correctly in SCORM Cloud, we'd like to take a closer look at your Rise 360 course.
You can share that with our support engineers privately, through a support case.
Looking forward to hearing from you!
Hi Steven,
Thanks for your response!
From what I can see, you are not receiving any score value. So, I suppose you are not tracking using the quiz result, which is why you aren't experiencing any trouble.This is how mine looks. I did it in one sitting. I failed te first attempt and passed the second.
Looking forward to hearing from you!
Hi CapperTheRose!
You're welcome. Thanks for following up!
My apologies for overlooking that step in my previous reply. However, after testing my Rise course again, set to 'Track using quiz result', I was still unable to replicate the same issue. After answering the question incorrectly, then again correctly all within the same launch session, SCORM Cloud recorded my progress accurately.
No worries! I'd like our support engineers to have a closer look at this issue, so I've opened a support case on your behalf. Also, I've sent you an e-mail with steps on how you can share a copy of your Rise 360 course privately with our team.
We'll delete it from our system as soon as we finish troubleshooting!
Update: Together with Articulate Support, I’ve identified the root cause. I’m sharing the details here so other users can benefit.
Multiple attempts in Rise 360 + CMI5 (Passed/Failed tracking) - important limitation
If you track a Rise 360 course in CMI5 with a final assessment that allows multiple attempts, and use the Passed/Failed verbs, the LMS will show outdated results.
Example:
- Learner fails the first attempt.
- Learner passes the second attempt in the same session.
- LMS (e.g., SCORM Cloud) still shows Failed from the first attempt.
The reason: CMI5 allows only one Passed or Failed verb per session. Rise currently sends Failed immediately when an attempt is failed, even if there are more attempts left, and that result remains even when the learner later passes.
We can’t use Passed/Incomplete, because our customers need to see who fails- both to identify knowledge gaps and to reset learners who have not passed.
Suggested fix (based on a workaround I used in Storyline):
- Send Passed immediately when the learner passes, regardless of attempt number.
- Send Failed only if it’s the final allowed attempt and the learner fails.
This would ensure the LMS always reflects the learner’s actual final result, without removing the ability to track failures.
