ADP Integration issues

Update timeline

1. investigating Apr 29, 2026, 01:53 PM UTC

   We are investigating an issue affecting some users upon login. Users may experience SSO errors when logging in with ADP This appears to be an issue directly with ADP. We will provide further updates as soon as available.

2. investigating Apr 29, 2026, 04:23 PM UTC

   We are currently investigating two related issues impacting our integration with ADP: Affected Services: JazzHR login via ADP (SSO) ADP candidate export to JazzHR Single Sign-On (SSO) Errors: Some users are experiencing errors when attempting to log in to JazzHR using ADP SSO. Candidate Export Issues: Candidate exports from ADP to JazzHR may be delayed or failing. At this time, we have reached out to ADP for additional details. We are unable to confirm an outage or incident on ADP’s side and are awaiting further information. Workaround Login Issues: As a temporary workaround, SSO can be disabled to allow users to log in directly to JazzHR using standard credentials. Please contact support for assistance. Export Issues: No native workaround available, please attempt to manually upload new hires to ADP and reach out to their support team if necessary. Next Steps Our team is actively monitoring the situation and has reached out to ADP to identify the root cause. We will provide updates as more information becomes available. Next Update: As soon as new details are confirmed.

3. identified Apr 29, 2026, 06:51 PM UTC

   Summary The issue affecting JazzHR logins via ADP Single Sign-On (SSO) and ADP candidate exports has been identified. Our team is actively working on a resolution. Affected Services JazzHR login via ADP (SSO) ADP candidate export to JazzHR Workaround SSO Login Issues: As a temporary workaround, SSO can be disabled to allow users to log in directly to JazzHR using their standard credentials. Next Steps We are actively implementing a fix and will provide additional updates as progress continues or once the issue has been fully resolved.

4. monitoring Apr 29, 2026, 07:49 PM UTC

   A fix has been successfully applied for the issue affecting JazzHR logins via ADP Single Sign-On (SSO) and ADP candidate exports. The issue originated within the integration flow and has now been addressed. Affected Services JazzHR login via ADP (SSO) ADP candidate export to JazzHR Current Status We are actively monitoring the platform to ensure continued stability and to confirm that all services are operating as expected. Next Steps Our team will continue monitoring and will share a Root Cause Analysis (RCA) within 7–10 business days.

5. resolved Apr 29, 2026, 08:51 PM UTC

   Resolved The issue affecting JazzHR logins via ADP Single Sign-On (SSO) and ADP candidate exports has been fully resolved. A fix was applied, and services are now operating normally. Affected Services JazzHR login via ADP (SSO) ADP candidate export to JazzHR Current Status We have completed post‑deployment monitoring and confirmed system stability. No further impact is expected. Follow‑Up A Root Cause Analysis (RCA) will be shared within 7–10 business days.

6. postmortem Apr 30, 2026, 04:25 PM UTC

   We want to share an update on a recent automation issue, including what happened, how it was resolved, and the steps we’ve taken to prevent it from happening again. ## Customer Impact From the evening of April 28 through the early evening of April 29 \(UTC\), customers using **ADP Single Sign-On \(SSO\)** were unable to log in to JazzHR via ADP. Login attempts failed during the OAuth callback step, preventing access through ADP authentication. In addition to SSO login failures, a smaller set of customers experienced issues with **ADP integration features** \(such as onboarding data pulls and candidate exports\) and a limited number of other third‑party integrations that rely on outbound connections. To minimize disruption, Customer Support temporarily disabled ADP SSO for affected tenants upon request, allowing end users to sign in using direct \(non‑SSO\) credentials until the issue was resolved. ## Root Cause A configuration change introduced as part of a routine infrastructure update caused the application to unintentionally route outbound traffic through an internal network proxy. Although the errors surfaced most visibly in ADP SSO login flows, the same underlying issue affected multiple outbound integrations during the same window. ## Resolution Once identified, the offending configuration change was fully reverted, restoring the previous behavior where outbound requests bypass the internal proxy unless explicitly required. After the corrected environment was redeployed: * Outbound connections immediately returned to normal behavior. * ADP SSO login success rates returned to baseline. * Impacted integrations recovered without requiring changes on the customer side. Customer Support then re‑enabled ADP SSO for affected tenants and confirmed restored functionality. ## Preventative Actions To reduce the likelihood and impact of similar issues in the future, we are implementing the following measures: 1. Improved Detection 2. Stronger Change Safeguards 3. Proxy Compatibility Checks 4. Faster Rollback Capabilities