Library insight admin area not rendering

Update timeline

1. investigating Feb 24, 2026, 08:53 AM UTC

   We are currently investigating this issue.

2. investigating Feb 24, 2026, 09:00 AM UTC

   We are continuing to investigate this issue.

3. identified Feb 24, 2026, 09:53 AM UTC

   We have identified an issue that affects a subset of customers and are working towards a resolution. Further updates will be posted here soon.

4. monitoring Feb 24, 2026, 10:53 AM UTC

   The incident has been successfully mitigated, and our team is actively monitoring the situation to ensure ongoing stability and performance. We are observing the systems to prevent any further disruptions.

5. resolved Feb 24, 2026, 11:06 AM UTC

   The incident has been resolved, and further information will be provided in a postmortem shortly. We apologize for the impact to affected customers.

6. postmortem Mar 02, 2026, 01:17 PM UTC

   # Investigation On February 23, 2026, at 11:00 AM CET, an issue was introduced affecting specific pages within the Library Insights section of the platform. The issue impacted administrators attempting to access certain pages within Library Content Insights, where the pages would crash and prevent data from being displayed. Other areas of the platform remained fully operational. The issue was detected on February 24, 2026, at 9:00 AM CET, after reports indicated that affected pages were not loading as expected. The engineering team started the investigation immediately. Through log analysis and reproduction in a controlled environment, the team identified that a recent software update had introduced a conflict within the rendering flow of the affected pages. More specifically, a recent update to the third-party dependency triggered an unintended infinite rendering loop when handling links embedded in a data table within Library Content Insights. This resulted in page crashes for administrators accessing those specific views. No data loss occurred, as the issue was isolated to the presentation layer. # Mitigation At 10:27 AM CET on February 24, 2026, the engineering team initiated a rollback of the recent update as a mitigation measure. The rollback was first validated in a staging environment to confirm that the rendering issue was resolved and that no additional side effects were introduced. Once validated, the rollback was prepared for deployment across production clusters. # Resolution At 12:04 PM CET on February 24, 2026, the rollback to the previous stable version was successfully deployed across all production clusters. Following deployment, administrators were able to access all pages within Library Insights without further crashes. The rendering loop was eliminated, and normal functionality was fully restored. # Impact and Scope The incident affected administrators with access to Library Content Insights across all production clusters. The issue was limited to specific pages within the Library Insights section and did not impact other platform functionality. No data was lost, altered, or compromised. The incident was strictly related to page rendering and presentation. # Post-Incident Actions To reduce the likelihood of similar issues in the future, we are implementing the following actions: • Introducing an end-to-end test specifically covering Library Content Insights to ensure critical user journeys are validated before deployment. • Expanding automated regression coverage for third-party dependency updates. • Enhancing release validation procedures for frontend dependency upgrades to better detect rendering-related regressions. These improvements will strengthen our ability to detect presentation-layer issues before they reach production.