We are working to promote a Workday Accounts direct connector from Sandbox to the next environment. The workday team configured everything per the documentation, and validated the same permissions for the service account were set as in Sandbox. We configured the Source in the same manner as well, and compared Sandbox and the next environment. The only difference was a secondary correlation value, which was not needed (and later removed from the Sandbox one with no effect)
When we go to aggregate the accounts, it finished in 7-10 seconds successfully, with 0 accounts returned. When we aggregated the entitlements, those were pulled in with the expected number returned.
We have since gone back and compared the values from both sides, and again found no differences that should affect the aggregation.
The documentation doesn’t state what end point it is using, but from the xpath, it appears to be the Get_Worker_Accounts endpoint. Thinking that testing that endpoint out with the credentials to see if any accounts are returned would be the next step.
Does anyone have a suggestion for what to try next? Or has anyone run into this issue?
Does the Workday Accounts connector also use the Get_Workers end point? We have tested the Get_Workday_Accounts endpoint and it is returning the users when testing outside of IDN, but IDN still returns 0 users. We saw references to Get_Workers in the log, and also what appears to be a 500 error when running the aggregation.
@madhukumar Thanks for that. I see that has the Get_Workers call, but not the Get_Workday_Accounts. It looks like that can be added easily. I assume that you run the Get Access Token, then the command?
This turned out to be a permission issue for the Service Account on the Workday side that was not staying set. The Workday team ended up resolving this before I was able to test any of the suggestions, so I am unable to mark them as a solution, but they seem like solid starts to debugging a similar issue.