I’m working with a customer and we’re suddenly running into an error aggregating Workday HR records using the SaaS Workday connector. We’ve narrowed it down to an issue with new hire records and we have a hunch that it might be related to data in one of the records we’re trying to read. Aggregations have been working for months and suddenly started failing yesterday morning.
We see the following when streaming the connector log:
03/03/2026, 10:23:57.565 DEBUG [connectorMessage] Response Received for Fetching Future Hire Records Page1
03/03/2026, 10:27:53.949 INFO [commandOutcome] Command failed with [ConnectorError] command canceled or expired: std:account:list, for connector version 44. output_count=0 output_bytes=0 keep_alive_count=0 state_count=0. Elapsed time 240092ms
03/03/2026, 10:27:59.925 INFO [commandOutcome] Command failed with [ConnectorError] error receiving response from connector: stream client connection is broken (connector process may have crashed): std:account:list, for connector version 44. output_count=0 output_bytes=0 keep_alive_count=0 state_count=0. Elapsed time 246068ms
We’re trying to read users who are being on-boarded within the next 7 days (something like 11 users total). The connector says it received a response fetching future hires, then it seemingly sits for 4 minutes before reporting the next two lines.
When we remove the Future Hire Offset, the aggregation succeeds and we receive all active users.
We’ve done a quick review of the user records in Workday and nothing obvious jumps out as a problem, but we don’t really know what we should be looking for.
We’ve opened a call with SailPoint support and Workday already, just hoping somebody else might have some ideas or has seen this before and knows what to do.
New wrinkle: we set up a new SaaS connector to the same endpoint keeping in all the default values except the Future Hire offset and it fails. Then we set up a VA-based connector and it works. So it looks like there’s almost definitely an issue in the SaaS connector.
I really hope the solution isn’t to migrate the primary Identity Source, but it’s looking that way.
just saw your update … I would still try the below. Maybe the backend is handling the data differently where it could still be a data issue that could be fixed. Otherwise, it sounds like you are on the right path working with support.
try using the sail command to tail the logs when you perform the aggregation and look for any suspicious xml in the data. It may be getting hung up on something someone copy and pasted on a user’s record.
We’re experiencing the same issue. Our config looks at future hires in the next 7 days. Our aggregation begins running without an issue, and once it gets to page 51, it fails after receiving a response. We opened a support case and are still waiting for a solution. Our workaround was to configure the VA-based connector, and it works as expected. I also reduced the future hire date to 0, and the aggregation still failed.
Hey Kevin - I’m hitting the same issue, tho a little less clear for when it fails versus succeeds, and it’s only started today after tons of aggs the last few weeks - did you have any luck staying on SaaS, or have to switch to VA?
This helped one of my customers, but the one I opened this topic about still can’t aggregate using the SaaS source. We switched to VA-hosted connectors and that’s working. We also have a support ticket open and are working with SailPoint on the SaaS issue as that was the preferred method of connecting.
We’ve also had to change our Workday source from a SaaS connector to the VA-based connector. The kicker unfortunately is we’re in the process of moving to Workday and this is part of our end to end testing, so the timing could be better. I did remember the S22 issue, but unfortunately the errors have been even less useful. Just things like “aborted”.
We also moved to VA, but eventually were able to get aggs through successfully on the SaaS connector after adding in a manager correlation. Have not re-removed it to verify it’ll still error without that, and the combination of “with future hires but without manager correlation” doesn’t sound like something that would interact like this…. but wanted to circle back and throw the info on the thread.