Cornerstone incident

Unable to access reports in Reporting 2.0 (US Swimlanes Production Environment)

Minor Resolved View vendor source →

Cornerstone experienced a minor incident on April 13, 2026 affecting Response Time and Response Time and 1 more component, lasting 4h 6m. The incident has been resolved; the full update timeline is below.

Started
Apr 13, 2026, 02:34 PM UTC
Resolved
Apr 13, 2026, 06:40 PM UTC
Duration
4h 6m
Detected by Pingoru
Apr 13, 2026, 02:34 PM UTC

Affected components

Response TimeResponse TimeResponse TimeResponse Time

Update timeline

  1. investigating Apr 13, 2026, 02:34 PM UTC

    US swimlanes are currently experiencing functional issues, including difficulties accessing reports. Clients with portals in this swimlane may encounter delays or disruptions while performing certain tasks. This issue is our top priority, and our teams are actively working toward a resolution. We appreciate your patience and recommend checking back periodically for updates as they become available.

  2. monitoring Apr 13, 2026, 02:43 PM UTC

    Our Engineering teams have identified the issue and deployed a fix to address it. We will continue to closely monitor the situation to ensure stability. Further updates will be shared through the Known Issue article and Statuspage. Thank you for your understanding and patience.

  3. resolved Apr 13, 2026, 06:40 PM UTC

    After a period of monitoring and no recurrences, we are considering this resolved.

  4. postmortem Apr 28, 2026, 05:14 PM UTC

    **Incident Summary:** Starting April 13th, 2026, intermittent errors were observed in reporting functionality across US Production swimlanes \(SL1, SL2, SL3, and SL5\). **Root Cause Analysis \(RCA\):** The issue was caused by the auto-scaling mechanism. Newly provisioned nodes were not fully ready to handle reporting requests, leading to processing delays and request timeouts. **Corrective Action:** Auto-scaling \(scale-out\) has been temporarily paused. The system is currently operating on a fixed, increased server capacity without scale-in or scale-out to ensure stability. **Preventive Actions:** * Capacity has been proactively increased to handle expected load without relying on auto-scaling. * Additional nodes are being utilized with auto-scaling disabled to maintain consistent performance. * Engineering teams are working on enhancements to improve node readiness and ensure seamless scaling in the future.