<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00009qLo1FCASOkta Classic EngineWorkflowsAnswered2023-11-17T20:47:33.000Z2023-11-16T15:47:05.000Z2023-11-17T20:47:33.000Z

StephenG.11459 (Customer) asked a question.

Users swapping to Non Okta-Mastered Users

All of our users are sourced from our HRIS system and created via Okta workflows (pre Anything as a Source, we built custom flows). They used to be synced with AD but we have severed that tie to AD.

 

Occasionally a user fails to be updated in Okta during our workflows and the error we get is "Unable to update user XXXX@YYYY.com because they are not Okta-mastered. See original error object for more information." Not every user is showing this error when they get updated. It seems to be a random selection of users.

 

Any ideas on why users will swap from Okta mastered to non Okta-mastered?


  • HI @StephenG.11459 (Customer)​ ,

     

    Without knowing more, users can change source based on profile mastery where depending on different factors they can switch from AD > Okta > HRIS...

     

    I am guessing that you may be getting an error like "user profile is sourced by a different system"... This is generally due by the attribute is not set as "inherit from Okta" is the Okta user profile.

     

    Please feel free to open a support case so we can work on this further

    Expand Post
This question is closed.
Loading
Users swapping to Non Okta-Mastered Users