Hi @Ankit_002 ,
Can you try your bulk operations again but use different names for your test accounts? The problem you were experiencing is that multiple accounts with the same name/email were being created at the same time in your testing. In a real world scenario, you typically wouldn’t expect to be hiring many users at the same time with the same name. If you are hiring multiple users at the same time with the same name (and they are getting the same non-incremented email value), this is when you can encounter a race condition due to the multithreaded processing. If 2 John Smiths are being processed at the exact same time, ISC may not see both emails that are being generated/used since the operations are happening simultaneously, which can lead to them both getting the same uniqueCounter when ISC is creating the provisioning plan for each account create operation.
If you are concerned about this possible race condition occurring, meaning you expect to onboard multiple users at the same time with the same name, you might want to look into adding a BeforeCreate rule to your AD source to check uniqueness against your Exchange server. This post details this process pretty well if it is something you would like to look into implementing to account for users with the same name being onboarded (having an account created for them) at the same time.
Thank you,
- Zach