Report Reliability and Troubleshooting
Check report permissions, source data, slow queries, empty reports, package data, and common report investigations.
Use this guide when a report is missing, empty, slow, confusing, or needs to be trusted before sharing.
Before you begin
You need access to the selected report and enough context to know what data should exist.
Before treating a report as wrong, confirm the selected report, filters, date range, organization, and source feature setup.
Check access and refresh issues
Refresh and retry
Reports refresh automatically when the report or filters change. If the report shows a retryable error, select Retry.
Error messages are grouped into practical causes:
| Message type | What it usually means | What to do |
|---|---|---|
| Session expired | Your auth token expired. | Refresh the page and sign in again. |
| Unable to load data | Network or service problem. | Check the connection and retry. |
| Query took too long | The result set is too broad. | Add filters or reduce the date range. |
| Invalid data format | The report received malformed data. | Contact support with the report name and filters. |
| Authentication error | Organization context is missing or stale. | Sign out and sign back in. |
| Unexpected error | The query failed outside a known category. | Retry, then narrow filters or contact support. |
Permission behavior
The report catalog is permission-filtered. If you have no report permissions, the sidebar can be empty.
Broad analytics permissions can show organization-wide data. Scoped analytics permissions can limit data to your own or team-related learners, groups, or courses. Wildcard permissions can also grant access when your organization uses them.
If you expect to see a report but cannot find it, ask an admin to review your analytics permissions and role configuration.
Check source data
Understand data dependencies
Reports are only as complete as the underlying activity data.
Use this checklist when a report looks wrong:
- Course reports depend on enrollment records, course status, progress, completion dates, modules, blocks, and category assignments.
- Course Builder block and quiz reports depend on Course Builder progress and interaction records.
- Learning path reports depend on path enrollments and node progress.
- Exam reports depend on exam attempts, responses, question metadata, grading, and score records.
- SCORM reports depend on package runtime data sent by the package.
- xAPI reports depend on xAPI statements and assessment response statements.
- Live learning reports depend on event/session records, enrollment records, platform sync, attendance, recording access, and instructor assignment.
- Certificate reports depend on certificate issuance and expiration records.
- Community reports depend on community threads, replies, votes, experts, and course associations.
- Group reports depend on group membership and manager relationships.
- System/audit reports depend on audit logs, login events, and usage events.
If a source feature is not enabled, unused, or not sending data, its reports can be empty.
Check package report gaps
SCORM and xAPI reports show what the package sends.
If package scores, responses, or completion values are missing:
- Confirm the learner launched the package.
- Confirm the package sends completion, score, or interaction data.
- Check launch window behavior if the package opens in a new tab or popup.
- Compare the package report to course completion settings.
- Re-test with a pilot learner if the package was recently updated.
Use reports for common investigations
Review completion for a course
- Open Course Completion Summary.
- Filter by the course.
- Check total enrolled, completed, in progress, not started, completion rate, and average time.
- Open Course Enrollments for learner-level rows.
- Save the report if you will review the same course again.
Find learners who need follow-up
- Open At-Risk Learners.
- Filter by risk level, group, manager, or overdue status if available.
- Sort by risk score or days inactive.
- Review stuck item and overdue columns.
- Export only if the follow-up owner needs a spreadsheet.
Review a learning path bottleneck
- Open Learning Path Node Analytics.
- Filter by learning path.
- Review completion rate, funnel rate, drop-off rate, bottleneck, and average time.
- Compare the problem node to nearby nodes.
- Use the path editor to adjust sequencing or content if the report confirms a real bottleneck.
Investigate exam quality
- Open Exam Summary to find exams with low pass rate, high retakes, or unusual difficulty.
- Open Exam Question Analysis for the same exam.
- Review difficulty index, correct count, attempts, and average time.
- Open Exam Response Details when you need individual response data or grading status.
Audit an admin change
- Open Audit Trail.
- Filter by action type or date range.
- Search table data for the admin, action, or affected resource.
- Export only the rows required for the audit record.
Verify and support report trust
Verify success
The report is trustworthy enough to share when:
- The selected report matches the investigation.
- Filters and date range are correct.
- The source feature is enabled and producing data.
- Blank values have a clear explanation.
- The recipient is allowed to see the rows.
- Any exported rows are limited to the data needed.
Troubleshooting
Check filters, date range, selected users, selected groups, selected content, and whether the source feature has data. For example, an xAPI report is empty if no xAPI statements were recorded, and a certificate report is empty if no certificates were issued.
SCORM and xAPI reports show what the package sends. Check the package settings, completion behavior, and whether the learner launched the package long enough for runtime data to be recorded.
Reduce the date range, filter by course, group, user, path, exam, or event, or choose a more specific report family.
Check the source object first: course completion settings, exam attempt records, package reporting, live learning attendance, certificate issuance, community activity, group membership, or audit logs.