Hi ,
We are experiencing an issue with scheduling the Workday Account Aggregation task.
When executed manually, the task runs successfully.
However, when we schedule it to run automatically, it succeeds on the second attempt, but then fails on the subsequent two attempts with the following error:
java.net.SocketTimeoutException: Read timed out.
Has anyone else encountered this issue or have suggestions on how to resolve it?
Thank you for your help!
So, when it is run manually at the same when the scheduled job was supposed to run, it works?
Maybe try increasing the timeout. Or change the scheduled time.
when you run it manually, does it split to run on multiple hosts? Is the host running manually and on schedule basis are same hosts?
When we are running manually, we are running in partion mode. When we are scheduled it also we are doing in partion mode.
Workaround, we did is instead of running on partion mode, we are running on one specific server and we increase connetion time out value. Now we dont see any failures.
We have increase timeout value in application.xml, now we dont see any issues.
Hi @reddyc9 ,
It seems your issue has been resolved, but I wanted to share my experience for future reference. In SailPoint, the Workday connector does not support partition enablement. If you enable it, it may work intermittently.
After consulting with the SailPoint support team, they recommended using aggregationThreadSize instead of partition enablement for the Workday and Workday Accounts connectors. I implemented this solution, and it functions similarly to aggregation partition enablement without any issues so far.
I hope this helps.
Thanks,