Workday aggregation failing at different timings

Which IIQ version are you inquiring about?

Version 8.3

Share all details related to your problem, including any error messages you may have received.

Workday aggregation is failing after processing few records when executed at certain time in the environment.
Its working when we retry the aggregation job at different timings. (we have to try multiple times and this resulting the backlog of identity refresh events getting processed next day)

Error in Aggregation tsk result: the Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time

Workday Vendor comments:

We have seen in the past where SailPoint sets very restrictive timeout settings that drop the connection before the response is received. It’s worth a quick review to confirm the setting in addition to temporarily increasing to see if it resolves the issue and at least allows traffic to flow.

Per the Knowledge Article, although their solution uses our API/Web Services like Get_Workers, etc., the solution is owned and initiated by them. Workday Support does not have any insight into their configurations nor do we log the Requests / Responses that they may submit. As a result, we always request an initial reach out to your SailPoint contacts to confirm:

Update from Sailpoint support:

In your application xml we can see timeout is set to 10. You can try increasing to 15 min or so, but 10 seems to be sufficient time to wait for response from server. So this might not be a recommended solution.

As per the error message it looks like workday API server is under maintenance and server is not reachable. There has to be something happening around 1am, that is causing this issue.

we did checked with the workday team if there are any daily maintenance tasks that could be running. They mentioned nothing major tasks are running at the time.

As workday aggregation is failing, we have other identity refresh events getting missed and all these tasks are sequentially run (First workday agg then identity refresh broken into multiple subtasks). timing is important for the workday aggregation to run, we cant change the timings. We are trying to increase the chunk size if it helps at the moment it is set to 99.

Any advise on the next steps.

I have seem some people using timeout to 30 and chunk size to 200 and avoiding the workday aggregation during the anticipated time period when workday is under maintenance or running some heavy activities mainly on weekends and some time in weekday as well .

Thanks @HemantSingh for your reply.
Should we increase the timeout and decrease the chunk size or is it the other way around?
Which is the recommended option ?

what chunk size you have configured … you can try with wait time 30 and chunk size to 200

Current the chunk size is configured to 99.

How to determine what values to be set is it trial and error only ?

Yes it’s trail and error only … that’s I used to do for this, some one may have better option.

1 Like

Thanks @HemantSingh for your reply.

We are on Identityiq v8.3, will the latest version of workday using restapi instead of soap help in resolving these timeout issues ?

I haven’t tried the REST API version … you need to do some research and POC on this. My be some other people have tried this.

1 Like