An Update User card can sometimes fail to update the user's profile even though the flow history says the card was successfully run in execution history.
- Okta Workflows
- Update User card
Currently, the Okta Users API has a limitation around multiple independent requests editing an individual user at the same time. Workflows cards are hitting Okta API endpoints behind the scenes, and if multiple "Update User" cards are running at the same time (or other pieces of the Okta configuration are editing the same user), the edits get dropped intermittently. Because it is a timing issue, it will not be consistent.
This is not always the cause of this issue, but it is the most common one.
The recommendation from an Okta Workflows perspective is to ensure that the Update User cards are not 'overlapping' when trying to edit an individual user.
- If multiple flows are performing edits on the same user at the same time, either:
- Combine the flows/edits into one Update User card to avoid multiple requests
- Space out the two edits by adding a Wait For function prior to one of them
- If something else is editing the users at the same time as the Workflow:
- The solutions can vary here depending on the other edits, but a Wait For function before the Update User can help if the timing is consistent
