You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a situation where we update a users profile using the userApi.updateUser api. We await this call to confirm that the update completed successfully. We then call userApi.listUsers to get the updated list of users (this happens less than a second after the update call) and would expect that call to include the updated user information, however it contains the old user information.
This is the exact call we make to the userAPI:
await this.client.userApi.listUsers({ search: entries.map((id) => id eq "${id}").join(' or '), });´
We initially thought it might be caching but apparently caching is not active for Collection requests.
Reproduction Steps?
call userApi.updateUser and update a user
almost immediately afterwards call userApi.listUsers
list of users returned will not include the latest information for the user that was just updated
SDK Versions
7.1.1
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
We have a situation where we update a users profile using the userApi.updateUser api. We await this call to confirm that the update completed successfully. We then call userApi.listUsers to get the updated list of users (this happens less than a second after the update call) and would expect that call to include the updated user information, however it contains the old user information.
This is the exact call we make to the userAPI:
await this.client.userApi.listUsers({ search: entries.map((id) =>
id eq "${id}").join(' or '), });
´We initially thought it might be caching but apparently caching is not active for Collection requests.
Reproduction Steps?
SDK Versions
7.1.1
Additional Information
No response
The text was updated successfully, but these errors were encountered: