11/15/2022 06:36 AM
We have implemented the following job chain to enforce the account creation order in different target systems.
Problem is that, when the chain executes, if there are no Office365 accounts to be provisioned the second provisioning job does not get executed.
How can we solve it? Both are multithreaded WSRETRYJOB.
11/15/2022 07:17 AM
1) If you are using Endpoint based selection for WSRETRY Job, Try switching to Advanced Config - Query based WSRETRY JOB for Office365AccountProvisioning & OktaAccountProvisioning Triggers
2) To the maximum possible extent, recommend not to put the Provisioning triggers in the Trigger chain to get a better performance. And Worst case if you still want to use it, Add your Provisioning Trigger as last entry in your trigger chain.
If it is possible to re-design, then try it in such a way to use a single separate Provisioning trigger, which will pick up only these two endpoints and setup a schedule for this.
Feel free to try out the recommendation and keep us posted.
11/15/2022 07:26 AM
Thank you, I will try the first suggested option.
Yes, we can possibly re-design the jobs to use a single provisioning trigger but I would still need to enforce the provisioning order on an endpoint-basis. Is it possible to do so with a single job? If yes, how?
11/15/2022 08:58 AM
Unfortunately using the advanced config, and then filtering the respective endpoints and task types there, did not solve the issue.
Are there other options to make the triggers work while still enforcing the provisioning order on an endpoint-basis?
11/17/2022 08:56 PM
what is reason for having 2 separate wsretry ? account creation dependency ?
11/18/2022 03:10 AM
yes, exactly, we have a dependency between two target applications that requires accounts to be created in a strict order (I'm aware this is not optimal, it's something we want to manage directly in Saviynt but that's not happening anytime soon).
11/18/2022 04:35 AM
11/18/2022 09:25 AM
I've tried it but no luck, just the first wsretry job is executed and the job chain remains in this status forever (no job end date)
11/18/2022 09:30 AM
11/18/2022 09:36 AM
and the same for the other jobs, changing the code. I've tested the jobs singularly and they execute correctly.
11/18/2022 10:34 AM