Intermittent Errors on Manage Candidates Page - US Swimlanes

Update timeline

1. investigating Mar 30, 2026, 07:38 PM UTC

   Some customers on US swimlanes (US SL1, US SL2, US SL3, US SL5) may be experiencing intermittent errors on the Manage Candidates page. Our team is actively investigating this as a top priority and will provide updates as more information becomes available.

2. monitoring Mar 30, 2026, 08:28 PM UTC

   Our engineering teams have implemented a fix and we have recovered. We will monitor for at least an hour before marking this incident resolved.

3. resolved Mar 30, 2026, 11:18 PM UTC

   The CSOD Technology Team observed a performance degradation affecting this swimlane. The problem began at 11:45 AM Pacific Time and was resolved at 12:55 PM Pacific Time. During this time, clients with portals on this swimlane may have experienced slow performance or intermittent errors while accessing the Manage Candidates page. After a period of monitoring we are considering this issue Resolved.

4. postmortem May 21, 2026, 04:23 AM UTC

   **Incident Summary:** On March 30th, 2026, the US PRD environment experienced intermittent issues impacting the Manage Candidate module. During this time, users were intermittently unable to access or use the functionality as expected. **Impact:** Customers experienced intermittent failures and degraded functionality within the Manage Candidate module. **Root Cause Analysis \(RCA\):** The issue was caused by an intermittent authentication header handling problem within the Manage Candidate application in the US PRD environment. Requests reaching the backend services were intermittently missing required internal authentication headers, resulting in repeated HTTP 401 authentication failures during page rendering. Investigation identified that some requests were instead processed using external authorization tokens with an unsupported algorithm, while the affected services expected internal RSA-based authentication tokens. This mismatch caused authentication validation failures across multiple backend calls required for rendering the Manage Candidates page, leading to intermittent customer impact. **Resolution:** The affected services recovered following mitigation actions performed by the engineering teams. Service health and customer impact were monitored after recovery to confirm platform stability before the incident was marked resolved. **Preventive Measures:** The following measures have been implemented to reduce the likelihood of recurrence: * Application stability checks have been reinforced to support faster detection and recovery during transient service interruption