Error loading pages in Omni - Something went wrong 500:Error

Update timeline

1. investigating Feb 18, 2026, 03:05 PM UTC

   Our monitoring picked up an increase in error rates and we have begun receiving some reports. We are actively investigating and working on mitigation

2. investigating Feb 18, 2026, 03:08 PM UTC

   We identified an unhealthy resource in our infrastructure and have applied a mitigation. We are seeing error rates decrease but we are continuing to monitor and investigate.

3. monitoring Feb 18, 2026, 03:21 PM UTC

   Error rates have stayed down since our mitigation was implemented. We are continuing to monitor.

4. investigating Feb 18, 2026, 04:20 PM UTC

   We are seeing increased application errors and are actively investigating.

5. identified Feb 18, 2026, 05:32 PM UTC

   Our team has identified a stuck transaction in our job queue, which was preventing work from being dispatched to our backend workers. We have cycled the affected component and are seeing recovery. Investigation continues and we will provide another update shortly.

6. monitoring Feb 18, 2026, 05:42 PM UTC

   Our mitigation efforts appear to be successful and we are seeing active recovery. We have identified the root cause as an infrastructure scaling event that introduced instability into our job processing pipeline. Queue depths are decreasing and we are continuing to monitor closely.

7. resolved Feb 18, 2026, 06:06 PM UTC

   This incident has been resolved. Query processing has stabilized, all backlogs have cleared, and we are no longer seeing any errors or delays.