Troubleshooting: Sync Disconnections
Administrators receive an email notification when a disconnection is triggered. This topic lists the causes and solutions for sync disconnections for both OAuth and password integration connection methods between Peakon and Workday.
Problem | Cause | Solution |
|---|---|---|
Integration System User (ISU) account is locked or disabled. | The integration fails if the ISU's account is locked or disabled. | Security: Security Administration domain in the System functional area.
|
Security permission not granted to ISU or ISSG. | User doesn’t have the correct security access in Workday to make any changes on the integration configuration. | Security: Security Configuration domain in these functional areas:
|
Expired password (password only) . | The user failed to update the ISU password before it expired. | Keep the ISU's password current. If Workday system passwords expire, update the ISU's password in Peakon to avoid authentication failures. Either maintain a static password or reconnect the integration with the updated password when it refreshes. To identify the authorizing user, name the integration system user clearly as related to Peakon. Use Workday's global search for user:peakon and verify the Signon History to confirm the integration's authorization.(Optional) To make an ISU's password exempt from expiration:Security: Security Administration domain in the System functional area.
|
Expired refresh token (OAuth only) . | The token created when you configured the API client for OAuth authentication has changed. | Security: Security Administration domain in the System functional area.
|
Workday service unavailable: Refresh token failure (OAuth only) .Unable to refresh access token due to communication issues, please reconnect. | Workday servers are experiencing above-average traffic. As a result, Workday overloads and invalidates Peakon tokens. | Security: These domains in the Integration and System functional areas:
|