We onboard new employees using technical rules. which creates tasks for AD account and exchange mailbox provisioning. Exchange mailbox creation depends on AD account.
We use a trigger chain for processing these tasks which has custom query jobs and WSretry jobs for AD and Exchange mailbox security systems. We added exchange provision job to be the last in the trigger chain. The job trigger and task processing was working fine in 5.5sp3.9. recently we upgraded to 5.5sp3.17 which doesn't allow to have multiple wsretry jobs in the chain and allows only one job at the end of the chain. so we ended up adding exchange mailbox system to the AD provision wsretry job trigger.
Now we are running into issue, more often the Exchange tasks completes before AD account task resulting in mailbox creation failure. looking for remediation options, is it possible to trigger exchange task only after the AD account task is completed.
@rushikeshvartak Thank you for the suggestion. But I don't think it will completely solve the issue.
Current trigger chain run every 15 minutes. if we schedule new trigger to run every 20 minutes, there is still possibility of exchange task completing before AD, if a create user request is submitted between this 5 minute window
Other option I tried is created a custom query which checks AD account, then populates a custom property on the user record. I set up a new technical rule checking the custom property to create exchange task. Created rule run job - to trigger the technical rule. Entire process its working.
Only concern is we're on 5.5sp3.17 now, and we are in process of moving to EIC, where custom query's and rule run jobs are deprecated. Not sure if it's worth to go with this option.