@Austin_Grimesposted in Compass, but the post does not seem to have comments open, so starting a discussion here on the same.
Workday connector aggregations are currently experiencing issues
SailPoint has identified an issue with Workday connector aggregations currently impacting some of our customers. After investigation, we’ve confirmed with Workday that the root cause of this issue resides on their end.
In the meantime, SailPoint has identified a potential workaround. You can update the retry settings on your Workday source by following the Workday troubleshooting document and applying the provided PATCH call.
PATCH /beta/sources/{id}
{
“op”: “add”,
“path”: “/connectorAttributes/retryErrors”,
“value”: [
“Connection reset”,
“503 Service Unavailable”,
“error code: 500”,
“502 Bad Gateway”,
“javax.net.ssl.SSLException: Read timed out”,
“java.net.SocketTimeoutException: Read timed”,
"Aggregation failed in one or more thread execution"
]
}
Please note that this workaround may not resolve the issue in all cases, though it has been successful for some customers. If you continue to experience problems, we recommend reaching out to Workday directly for further assistance.
The linked Workday Community Alert is behind Workday Community authentication, which not all SailPoint admins have access to, so I’ll share that here as well:
@Austin_Grimes you have “java.net.SocketTimeoutException: Read timed” on your list of retryErrors, was that truncated inadvertently? or was Read timed the intended exception message?
In addition, I’ve been seeing the following errors that are not included in your list:
org.apache.http.NoHttpResponseException: wd5-services1.myworkday.com:443 failed to respond
error code: 520 (a Cloudflare-specific message indicating an unexpected response from the website’s origin server)
org.apache.http.ConnectionClosedException: Premature end of chunk coded message body: closing chunk expected
Are these messages that other folks are seeing as well? Should these also be added to the retryErrors list?
Did you ever get a response for this list? We are seeing the last one (Closing Chunk Expected) in an IIQ environment and I was wondering if I should add those to their Retry as well.
