Known Issues - Ciphr LMS

The following is a list of currently tracked known issues affecting Ciphr LMS, each entry includes a brief description of the issue along with a suggested workaround if one has been identified.

This list is refreshed weekly and was last updated on 1st July 2026.

When a user's activity status changes (such as completing an activity that was previously not started), the updated result fails to sync to HR. The LMS record updates correctly but the corresponding HR record remains at the previous status.

This is most likely to affect customers who assign activities directly to users rather than through learning plans.

There is currently no workaround for this issue.

When a Learning Activity's short description wraps across multiple lines, the text is cut off in the activity details view with no option to scroll or expand it.

Until this is resolved, we recommend keeping short descriptions brief enough to avoid text wrapping, or moving any additional detail into the full Description field.

When a learning plan or journey is set to launch automatically on login, it fails to do so for individually assigned users. Updating the User Development Plan resets the mandatory and launch on login settings, preventing the journey from launching as expected.

Until this is resolved, avoid using the Update User Development Plan option for any individually assigned mandatory journeys.

When running either report, an error is returned instead of results. This is most likely to affect customers with large volumes of data.

Until this is resolved, try narrowing the date range or limiting the activities selected to allow the report to run.

When adding or editing organisation structures, the page times out before completing. This affects standalone LMS customers with large volumes of organisation structures.

Until this is resolved, reducing the number of organisation structures may help prevent the timeout from occurring.

Some users may occasionally see an error immediately after clicking Log In. The issue is intermittent and no consistent pattern has been identified.

Until this is resolved, users should attempt to log in again if the error appears, as it does not occur consistently.

The progress percentage shown in the Learning Progress Report may differ from the progress displayed against a learning plan or journey. This is caused by the Development Plan List using a different calculation method to the rest of the system.

There is currently no workaround for this. We recommend using the Learning Progress Report as the most accurate reflection of a user's progress until this is resolved.

When users launch and interact with an ELFH activity, multiple completion statuses are randomly sent back to the LMS, resulting in inconsistent or duplicate status updates. This also occurs when closing the activity tab.

There is currently no workaround for this issue. We recommend users check their completion status in their learning record after completing an ELFH activity and contact their administrator if it does not appear correct.

The pie chart in the Activity Status List Report does not update when the Assignment filter is changed, always displaying the same data regardless of the filter applied to the report.

Until this is resolved, export the report to Excel to view accurate figures that correctly reflect the selected filter.

Team Learning Progress widgets may intermittently fail to load within the timeout period, resulting in incomplete or missing data in the widget.

Refreshing the page can often resolve the issue and allow the widget(s) to load successfully.

When a user fails an assessment, their score may be recorded incorrectly, showing a value that does not match the percentage of correct answers given. This does not appear to affect pass results, which score correctly.

There is currently no workaround for this issue. Affected users should retake the assessment, as scores appear to record correctly on a passing attempt.

The 'Approaching Renewal' column is not displayed in the Activity Status List Report, either in the UI or when exported to Excel.

There is currently no workaround for this issue.