0D51Y0000ATusHqSQJOkta Classic EngineLifecycle ManagementAnswered2024-04-15T09:50:26.000Z2021-02-12T17:28:30.000Z2021-02-12T17:29:59.000Z

zwoql (zwoql) asked a question.

Consecutive calls fail for update user profile => get users by attribute (race condition?)

I'm wondering if there is some sort of known race condition going on when making subsequent calls to update a specific user and getting users based on a custom attribute?

 

  • We are making a synchronous call to Okta's /api/v1/users/ api to update a user's name.
  • We then make sequential call /api/v1/users?search=profile.someId to get all users by a companyId soon after we get a 200 response from okta. Note: We are able to watch our network tab and indeed, the subsequent call waits for a 200 to return.
  • We are returned the old user value 1/10 times

 

Any insight would be appreciated.

 


  • zwoql (zwoql)

    Also, we are not caching okta users on the server.

This question is closed.

Recommended content

No recommended content found...