During the Learn Service deployment, a database migration introduced a schema change that removed a database column still required by another platform component.
As a result, the affected component was no longer fully compatible with the updated database schema, which caused learner progress management actions to fail or remain loading without completing.
The issue was related to a deployment sequencing dependency between platform components. This dependency was not identified early enough during the release validation process.
Once the root cause was identified, we applied a hotfix to restore the required database column.
This restored compatibility between the affected platform components and resolved the issue affecting learner progress management actions.
To reduce the risk of similar incidents in the future, we are implementing the following improvements:
Improved release dependency checks
We are strengthening release validation to ensure dependencies between platform components are identified and confirmed before deployment.
Updated database migration guidelines
We are formalizing additional safeguards for database schema changes, especially when removing database fields that may be used by multiple platform components.
Additional deployment review automation
We are introducing automated checks to help identify potentially risky database migration patterns before release.
Stronger release readiness validation
We are improving release readiness checks to ensure critical validation steps are completed before production deployment.
We apologize for the disruption this caused and appreciate your patience while our teams investigated and resolved the issue.