Registrations and Attempts
A registration is a learner against a package. An attempt is one run at it.
Where to find it
Architect Panel → eLearning:
- Courses & Assignments — the course console — courses, units, assignments
- Learner Records — a learner’s registration against a package
- Course Attempts — each attempt at a package
- Course Sessions — individual launches
- Learning Objectives — objective-level results
The registration
Holds the current position: status, completion status, success status, raw and scaled scores with their minimum and maximum, progress measure, attempt number, total time, where the learner got to, their suspend data, and the entry and exit modes.
It is the answer to "how is this person doing" — one row, current.
The attempts
Each attempt records its own number, status, completion and success, scores and session time, with a start and end. So a learner who failed twice and passed on the third go has three attempt rows and a registration showing a pass.
Why both exist
Because the questions are different. "Are they compliant" is the registration. "How hard did they find it" is the attempts, and a course where most people pass on the third attempt is a course with a problem.
Lesson location and suspend data
Where the learner got to and the content’s own bookmark. These are what make resuming work, and they are the first things to look at when somebody says a course keeps restarting.
Empty suspend data on a package that should resume means the content is not saving its position.
Attempt count is a quality signal
Look at the distribution, not the average. Most people passing first time with a few taking two attempts is healthy. Most people taking three is a badly written assessment, ambiguous questions, or content that does not teach what is tested.
When a learner disputes a result
Go to the attempt, not the registration. It shows what happened on that specific run — the score, the time, when it started and ended — which usually resolves the question immediately.
If the dispute is about a specific question, the interaction records go further still.
Zero-time completions are worth checking
An attempt completed in seconds is either a package that reports completion on launch, or somebody who found a way past the content. Either is worth knowing about, and both look identical in a completion report.
Records belong to the learner
They are personal data about somebody’s performance. Who can see them should be deliberate — a manager seeing their team is reasonable, everybody seeing everybody is not.
Worked example
A training team reviews the attempt distribution for each course quarterly. One assessment showed most learners passing on the third attempt; reviewing the interactions found two questions testing material the module never covered.
Recommendations
- Registration for status, attempts for difficulty.
- Read the attempt distribution, not the average.
- Check zero-time completions.
- Restrict who can see learner records.