Cornerstone Incident History

Queues have been caught up across all environments and this issue is now Resolved.

The backlog of queued events has largely cleared across all Production environments. We are now reviewing the queues in all Pilot and Stage environments and taking action to expedite processing of any remaining backlog.

We have taken action to expedite the processing of the backlog of queued events, and most swimlanes have now fully recovered. We will provide a final update once processing has fully returned to normal across all swimlanes.

We are continuing to investigate this issue.

Customers across all swimlanes may experience delayed or stuck processing of queued events and background jobs (i.e., Content Uploader, Emails, Reporting, Roster Submissions etc.). We are actively investigating this issue as a top priority, and will provide regular updates until it is fully resolved.

**Issue Summary:** On July 13 and July 15, 2026, a production issue intermittently affected the Career Site experience across the US production swimlanes \(SL1, SL2, SL3, and SL5\). During the affected periods, some job seekers were unable to access career site services or view job postings. ‌ **Root Cause:** The issue was caused by performance degradation within the Job Search service that supports career site job listings. Two contributing factors were identified: * Timezone-related database queries experienced contention during periods of increased traffic, causing requests to queue and, in some cases, time out. * A configuration check used to determine whether timezone adjustments should be applied was executed multiple times within each user request, creating additional system load. The combined impact of these conditions reduced the service’s ability to process requests efficiently during higher-traffic periods. ‌ **Corrective Action:** _Temporary Fix_ As an immediate mitigation on July 13, the processing capacity of the Job Search service was increased by raising the number of allocated tasks in each region. On July 15, the issue recurred after an automated deployment reset the increased task allocation. Engineering subsequently updated the deployment configuration to maintain the allocation until the long-term solution is implemented with August 7 patch. _Long-Term Fix_ The long-term solution with the August 7 patch will include: * Optimizing timezone-related database queries to prevent requests from blocking one another. * Caching configuration and timezone data to reduce repeated database calls. * Improving the efficiency of processing job posting, timezone, and hiring manager information. ‌ **Preventive Measures:** To reduce the risk of recurrence, Cornerstone has taken the following actions: * Enhanced monitoring and alerting will be added to identify early signs of service degradation. * Load testing will be performed under peak-traffic conditions to validate the stability and performance of the Career Site Experience.

Following an extended monitoring period, our Engineering team has confirmed that the issue has been successfully resolved. The preventive measures implemented have proven to be effective and reliable throughout the monitoring period, and the affected Career Sites continue to operate as expected. To further strengthen the platform and help prevent similar issues in the future, our Engineering team is working on additional backend system and database optimizations. These improvements are scheduled to be deployed as an off-cycle release on 07 Aug 2026. We will now conclude active monitoring and consider this incident resolved. The associated Known Issue (https://cornerstoneondemand.lightning.force.com/lightning/articles/Knowledge/KNOWN-ISSUE-CSX-No-Jobs-Displayed-on-Career-Site-for-US-Swimlanes-Production) will remain in Monitoring status until the scheduled 07 Aug 2026 release has been completed, after which it will be closed. A detailed Root Cause Analysis (RCA) will be published within the next 7–10 business days. Thank you for your patience, understanding, and cooperation throughout this matter!

We have received reports that the issue has resurfaced(https://status.csod.com/incidents/zjk01s8bh79l). Our Engineering team investigated promptly and has implemented the necessary corrective measures. We will continue to closely monitor the environment to ensure the issue remains resolved and the career sites remains stable.

**Issue Summary:** On July 13 and July 15, 2026, a production issue intermittently affected the Career Site experience across the US production swimlanes \(SL1, SL2, SL3, and SL5\). During the affected periods, some job seekers were unable to access career site services or view job postings. ‌ **Root Cause:** The issue was caused by performance degradation within the Job Search service that supports career site job listings. Two contributing factors were identified: * Timezone-related database queries experienced contention during periods of increased traffic, causing requests to queue and, in some cases, time out. * A configuration check used to determine whether timezone adjustments should be applied was executed multiple times within each user request, creating additional system load. The combined impact of these conditions reduced the service’s ability to process requests efficiently during higher-traffic periods. ‌ **Corrective Action:** _Temporary Fix_ As an immediate mitigation on July 13, the processing capacity of the Job Search service was increased by raising the number of allocated tasks in each region. On July 15, the issue recurred after an automated deployment reset the increased task allocation. Engineering subsequently updated the deployment configuration to maintain the allocation until the long-term solution is implemented with August 7 patch. _Long-Term Fix_ The long-term solution with the August 7 patch will include: * Optimizing timezone-related database queries to prevent requests from blocking one another. * Caching configuration and timezone data to reduce repeated database calls. * Improving the efficiency of processing job posting, timezone, and hiring manager information. ‌ **Preventive Measures:** To reduce the risk of recurrence, Cornerstone has taken the following actions: * Enhanced monitoring and alerting will be added to identify early signs of service degradation. * Load testing will be performed under peak-traffic conditions to validate the stability and performance of the Career Site Experience.

Following a period of monitoring, the implemented fix has remained stable, and this issue has been confirmed as resolved.

Our Engineering team has identified the root cause of the issue and has successfully implemented a fix. Internal and External Career Sites are now functioning as intended, and job requisitions are once again visible to candidates. We will continue to closely monitor the environment to ensure ongoing stability and prevent any recurrence. Thank you for your patience and understanding.

An issue has been identified affecting customers hosted on US Swimlanes in the Production environment where Internal and External Career Sites do not display any job requisitions. Although job requisitions remain in an Open status, they are not searchable or visible on the Career Site, resulting in blank job listing pages for candidates. Our Engineering teams have identified this as a high-priority issue and are actively investigating and working to restore normal functionality as quickly as possible. Please check back periodically for additional updates, which will be posted as they become available.

**Issue Summary:** On July 7, 2026, users across all Production regions experienced intermittent service degradation due to elevated background processing activity. The increased workload temporarily affected platform responsiveness and caused delays in certain application workflows. **Root Cause:** The issue was caused by an unexpected surge in background processing requests, which generated a significantly higher workload than anticipated. The elevated processing volume temporarily reduced system throughput, resulting in increased processing times and intermittent service degradation across multiple regions. **Corrective Action:** As an immediate mitigation, non-essential background processing was temporarily restricted to reduce system load and prioritize critical requests. Additional optimization activities were performed to accelerate queue processing and restore normal system performance. These actions stabilized the environment, and processing rates returned to expected levels. **Preventive Measures:** To reduce the risk of recurrence, Cornerstone has updated operational procedures for managing large-scale background processing activities. These updates are intended to better control processing volume and reduce the likelihood that unexpected workload surges will impact Production services.

All queues have been caught up and after a period of monitoring we are considering this issue Resolved.

The backlog of queued events continues to decrease as events are processed. Our teams are closely monitoring activity to ensure recovery continues to progress as quickly as possible. We will continue to provide updates until the backlog has cleared.

We are seeing the backlog of queued events begin to decrease. We are working on taking additional action to reduce the backlog more quickly and accelerate recovery. We will continue to provide updates as progress is made.

Customers across all swimlanes may experience delayed or stuck processing of queued events and background jobs (i.e., Content Uploader, Emails, Reporting, etc.). We are actively investigating this issue as a top priority, and will provide regular updates until it is fully resolved.

After careful review and monitoring, we’ve determined this does not meet the definition of a Severity2: emails are firing as expected, and Mailspike’s blacklisting is having only a minor effect on email delivery for customers in the impacted IP—primarily those who rely on Mailspike for inbound email filtering. As a result, the incident is being closed on the Status page, and any further communications will be handled as a Severity3 via the existing Known Issue article: https://cornerstoneondemand.my.site.com/s/articles/Known-Issue-CSX-UK-Email-IP-blacklisted-by-Mailspike CSOD technical teams will continue working closely with Mailspike to address the underlying concerns.

We are continuing to work closely with the vendor to obtain confirmation on the IP delisting request. We will provide the next update as soon as we receive any new information.

We are continuing to work closely with the vendor to obtain confirmation on the IP delisting request. We will provide the next update as soon as we receive any new information.

Cornerstone UK's email sending IPs have been temporarily blacklisted by Mailspike, a community-oriented IP reputation authority, due to a high number of email delivery failures originating from certain customer accounts. During this time, emails may fail to deliver. This is our top priority, and we are working closely with the vendor to resolve the problem as soon as possible. Please check back periodically for additional updates, which will be posted as they become available.

We are continuing to work closely with the vendor to obtain confirmation on the IP delisting request. We will provide the next update as soon as we receive any new information.

We remain actively engaged with the vendor and are awaiting confirmation on the delisting. We will continue sharing updates as they become available.

We remain actively engaged with the vendor and are awaiting confirmation on the delisting. We will continue sharing updates as they become available.

We remain actively engaged with the vendor and are awaiting confirmation on the delisting. We will continue sharing updates as they become available.

We remain in contact with Mailspike while awaiting confirmation of the delisting. Further updates will be provided in due course.

We’re actively engaging with Mailspike and awaiting their reply regarding our delisting request. Regular updates will be provided until the matter is completely resolved.

Cornerstone UK's email sending IPs have been temporarily blacklisted by Mailspike, a community-oriented IP reputation authority, due to a high number of email delivery failures originating from certain customer accounts. During this time, emails may fail to deliver. This is our top priority, and we are working closely with the vendor to resolve the problem as soon as possible. Please check back periodically for additional updates, which will be posted as they become available.

After careful review and monitoring, we’ve determined this does not meet the definition of a Severity2: emails are firing as expected, and Mailspike’s blacklisting is having only a minor effect on email delivery for customers in the impacted IP—primarily those who rely on Mailspike for inbound email filtering. As a result, the incident is being closed on the Status page, and any further communications will be handled as a Severity3 via the existing Known Issue article: https://cornerstoneondemand.my.site.com/s/articles/Known-Issue-CSX-UK-Email-IP-blacklisted-by-Mailspike CSOD technical teams will continue working closely with Mailspike to address the underlying concerns.

We are continuing to work closely with the vendor to obtain confirmation on the IP delisting request. We will provide the next update as soon as we receive any new information.

We are continuing to work closely with the vendor to obtain confirmation on the IP delisting request. We will provide the next update as soon as we receive any new information.

Cornerstone UK's email sending IPs have been temporarily blacklisted by Mailspike, a community-oriented IP reputation authority, due to a high number of email delivery failures originating from certain customer accounts.During this time, emails may fail to deliver. This is our top priority, and we are working closely with the vendor to resolve the problem as soon as possible. Please check back periodically for additional updates, which will be posted as they become available.

We are continuing to work closely with the vendor to obtain confirmation on the IP delisting request. We will provide the next update as soon as we receive any new information.

We remain actively engaged with the vendor and are awaiting confirmation on the delisting. We will continue sharing updates as they become available.

We remain actively engaged with the vendor and are awaiting confirmation on the delisting. We will continue sharing updates as they become available.

We remain actively engaged with the vendor and are awaiting confirmation on the delisting. We will continue sharing updates as they become available.

We remain in contact with Mailspike while awaiting confirmation of the delisting. Further updates will be provided in due course.

We’re actively engaging with Mailspike and awaiting their reply regarding our delisting request. Regular updates will be provided until the matter is completely resolved.

Cornerstone UK's email sending IPs have been temporarily blacklisted by Mailspike, a community-oriented IP reputation authority, due to a high number of email delivery failures originating from certain customer accounts.During this time, emails may fail to deliver. This is our top priority, and we are working closely with the vendor to resolve the problem as soon as possible. Please check back periodically for additional updates, which will be posted as they become available.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Users may experience a slight degradation in service like increased latency and/or portals may be temporarily unavailable for up to 20 minutes while we deploy the latest Software Application Code. We thank you for your cooperation as we continue to add best in class features and functionality to the Cornerstone Cloud Platform.

**Incident Summary:** On 22nd June 2026, users in the EU region experienced intermittent service degradation caused by DNS resolution failures. Our LXP applications were unable to reliably resolve internal service names, resulting in connectivity issues and increased response times. A subset of customers experienced HTTP 504 Gateway Timeout errors during the incident window. **Impact:** A subset of EU customers experienced service degradation, including increased latency and 504 Gateway Timeout responses. Internal application communication was intermittently disrupted due to failed DNS lookups. Customer transactions and requests dependent on affected services were delayed or unsuccessful until DNS functionality was restored. **Root Cause:** The issue was caused by resource saturation and degraded performance of DNS within the EU cluster. As DNS response times increased, application pods experienced delays and failures when resolving internal and external hostnames. This impacted service-to-service communication and request processing across the environment. **Corrective Actions:** As an immediate mitigation, additional resources were allocated to the DNS pods to handle the sudden spike in DNS traffic and restore service stability **Preventive Actions:** The team is re-evaluating DNS configuration and scaling parameters, reviewing DNS traffic patterns, and adjusting resource allocations based on updated capacity planning.

The CSOD Technology Team observed a performance degradation affecting production portals across EU. The problem began at 10:35 PM PST and was resolved at 11:30 PM PST. During this time, clients could not enter LXP portals and encounter 504 Gateway Timeout Error.

**Incident Summary:** On June 28th, 2026, at 11:24 AM PT, users in the UK Production environment experienced intermittent service degradation impacting session management functionality. The issue resulted in reduced service availability and intermittent failures while accessing affected applications. **Impact:** Users experienced intermittent service disruption and degraded application responsiveness due to instability within the session management service. Some requests were impacted during the incident window, resulting in temporary failures across affected portal functionalities. **Root Cause Analysis \(RCA\):** The issue was related to transient service instability following infrastructure changes, which impacted the availability and responsiveness of the session management service. During recovery, service initialization delays affected the ability to restore full processing capacity within the expected timeframe, resulting in intermittent service impact. **Resolution:** As an immediate mitigation, service traffic handling was adjusted to allow the affected components to stabilize and recover successfully. Once service capacity was restored and stability was confirmed, normal traffic processing resumed and application performance returned to expected levels. **Preventive Actions:** The following measures have been implemented to reduce the likelihood of recurrence: * Service startup and recovery behavior are being reviewed to improve restoration time during availability events. * Additional monitoring and validation checks are being enhanced to improve visibility into service health and recovery patterns.

This incident has been resolved.

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

We continue to work on the fix for this issue.

Users report issue on Career Site as well. We keep on working on the problem.

UK swimlanes are experiencing an intermittent service disruption. This is our top priority and we are working to resolve the problem as soon as possible. Please check back periodically for additional updates, which will be posted as they become available.

This incident has been resolved.

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

We continue to work on the fix for this issue.

Users report issue on Career Site as well. We keep on working on the problem.

UK swimlanes are experiencing an intermittent service disruption. This is our top priority and we are working to resolve the problem as soon as possible. Please check back periodically for additional updates, which will be posted as they become available.

All queues have been caught up and after a period of monitoring we are considering this issue Resolved.

The backlog of queued events continues to decrease as events are processed. Our teams are closely monitoring activity to ensure recovery continues to progress as quickly as possible. We will continue to provide updates until the backlog has cleared.

We are seeing the backlog of queued events begin to decrease. We are working on taking additional action to reduce the backlog more quickly and accelerate recovery. We will continue to provide updates as progress is made.

Customers across all swimlanes may experience delayed or stuck processing of queued events and background jobs (i.e., Content Uploader, Emails, Reporting, etc.). We are actively investigating this issue as a top priority, and will provide regular updates until it is fully resolved.