Minor Issue - Functionality - Error accessing xAPI Statement Viewer across FRA, UK, and US Swimlanes

Update timeline

1. investigating Sep 04, 2026, 07:53 PM UTC

   This swimlane is experiencing some functional issues accessing the xAPI Statement viewer and may have issues with xAPI statement processing. Clients with portals in this swimlane may experience delays or issues executing some tasks. This is our top priority and we are working to resolve the problem as soon as possible. Please check back periodically for additional updates, which will be posted as they become available.

2. investigating Sep 04, 2026, 09:48 PM UTC

   We are continuing to investigate this issue and will share an update at least every 2 hours or until we have more.

3. identified Sep 04, 2026, 11:02 PM UTC

   Cornerstone Engineering has identified the issue and is currently working on a fix. We will update once the issue is Resolved.

4. identified Sep 05, 2026, 01:06 AM UTC

   We are still working on a fix and will confirm once it has been successfully deployed. This remains a top priority for our teams and we will continue sharing updates as they become available or at least every 2 hours.

5. monitoring Sep 05, 2026, 01:50 AM UTC

   A fix has been deployed and we are seeing no errors. We will monitor for 1 hour before placing this in a Resolved status.

6. resolved Sep 05, 2026, 03:44 AM UTC

   After a period of monitoring with no repeat occurrences we are marking this incident Resolved. A formal Root Cause Analysis will be available 7-10 business days from Resolution.

7. postmortem Sep 23, 2026, 07:07 AM UTC

   **Root Cause Analysis** **Issue:** On September 4th, 2026, the xAPI service started returning errors during authentication of incoming requests. **Impact:** The issue prevented affected users from successfully loading or interacting with xAPI statement data, disrupting normal viewing functionality. **Root Cause:** The Public API Gateway infrastructure was updated to address a gap related to authentication for some endpoints \(not xAPI\). This change had an unintended impact on the xAPI service and caused a system regression. **Corrective Action:** On September 4th, 2026, the Public API Gateway infrastructure was rolled back to an earlier version which did not have this regression. **Preventive Action:** * On September 4th, 2026, changes were reverted entirely and a different mitigation was performed to ensure that behavior expected by xAPI is maintained. * Additional automation is being added to the Public API Gateway which asserts that the expected behavior of xAPI is not regressed.