Call: getUserByExternalId() sometimes doesn't work

[StanBarrows]

Even with a set external_id the getUserByExternalId() sometimes doesn't work when a user is active. With inactive user it works.

[birdcar]

Hey, sorry for the super delayed response here 😬

I dug into this on both the SDK and API side. The SDK implementation is correct; it's just hitting GET /user_management/users/external_id/{externalId} which is the right endpoint. On the API side, the lookup queries by external_id and environment_id with no status filtering at all, so active vs inactive users shouldn't make any difference.

I wasn't able to reproduce this or find a code path that would explain the behavior you saw. My best guess is it was a transient issue at the time you hit it.

Are you still seeing this? If so, could you share:

• Which environment (staging vs production) you're querying against
• Whether the external_id was set at user creation or added via updateUser after the fact

That'd help me narrow things down. If it's resolved itself, totally fine to close this out.

[StanBarrows]

Hi @birdcar,

Yes, the issue is still there and it's on all our environments. We caught it now by code. We set the external ID on user creation, but it seems that follow-up requests run into this problem when trying to get the user by the set external ID.

Best regards
Sebastian