An AD attribute value is missed in AD account creation as part of Non employee source driven lifecycle workflow

we ran into issue where 3 users miss 1 key attribute (customized) at AD (the attribute has blank value). however on the same day (10/31) there were other 2 users whose attribute were populated with the right values.

Just want to find out if anybody runs into the similar issue

Here is what we setup for those users.

  1. Non-Employee source - we invoke API to create Non-Employee source account under this source.
  2. Identity Profile - triggers identity creation for any new account in the Non-Employee source
  3. the LCS (the lifecycle state) Active triggers the AD account creation.

Hi @charlieliujcn ,

How are you populating the customized attribute in AD? Do you have any transforms or rule in place?