The reporting 2.0 is returning zero results

Update timeline

1. investigating Jun 11, 2026, 01:55 PM UTC

   We are currently investigating the issue.

2. identified Jun 11, 2026, 02:13 PM UTC

   The issue has been identified, and a fix is currently being implemented.

3. identified Jun 11, 2026, 02:25 PM UTC

   We are continuing to work on a fix for this issue.

4. monitoring Jun 11, 2026, 02:26 PM UTC

   A fix has been implemented and we are monitoring the results.

5. monitoring Jun 11, 2026, 02:26 PM UTC

   We are continuing to monitor for any further issues.

6. monitoring Jun 11, 2026, 02:53 PM UTC

   We are continuing to monitor for any further issues.

7. resolved Jun 11, 2026, 02:54 PM UTC

   This incident has been resolved now.

8. postmortem Jul 02, 2026, 06:58 AM UTC

   **Incident Summary:** On June 11th, 2026, clients in the US Production environment \(SL1, SL2, SL3, and SL5\) experienced intermittent reporting errors for a brief duration. During the incident window, users encountered delays and intermittent failures while accessing reporting functionality, with a subset of reporting requests timing out. **Root Cause Analysis \(RCA\):** The issue was caused by a temporary capacity management and workload distribution inefficiency during a period of changing demand. This resulted in increased request processing times within the reporting service, leading to intermittent reporting failures and request timeouts. **Resolution:** Service capacity was stabilized by maintaining increased server capacity, ensuring sufficient resources were available to process reporting requests. Following this change, reporting functionality returned to normal operation. **Preventive Actions:** * Increased baseline service capacity to better support workload demands * Adjusted capacity management settings to provide more consistent performance during periods of fluctuating demand