On March 8th, 2024, internal monitoring tools at Cornerstone flagged latency concerns, potentially affecting clients hosted in US SL1 & SL2 Prod swimlanes accessing Reporting 2.0 intermittently.
Promptly, Cornerstone engineers launched an investigation, pinpointing a caching issue within one of the authorization services. Swift action ensued as the team reset the service, swiftly resolving the problem.
To forestall similar incidents and mitigate future risks, Cornerstone has enacted additional corrective measures. These include configuration optimization changes deployed in production, aiming to prevent recurrence of such issues.