# Disassociate pending users

**URL:** <https://devforum.zoom.us/t/disassociate-pending-users/112534>\
**Category:** Users and Groups\
**Created:** [June 25, 2024, 1:14pm UTC](https://devforum.zoom.us/t/disassociate-pending-users/112534 "2024-06-25T13:14:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![marius.toko](https://avatars.discourse-cdn.com/v4/letter/m/3ab097/32.png) [@marius.toko](https://devforum.zoom.us/u/marius.toko)\
**Post date:** [June 25, 2024, 1:14pm UTC](https://devforum.zoom.us/t/disassociate-pending-users/112534/1 "2024-06-25T13:14:41Z")

</div>

I’m facing some issue and i want to know if this is a normal behavior. Seems like a bug ?  
After deleting a pending user with this : /users/userId?action=disassociate  
the API will confirm the user does not exist anymore after a GET.  
But if i recreate again the same user and try another delete i will get :  
“code”: 429, “message”: “Too many concurrent requests. A request to disassociate this user has already been made.”

It looks like the system keeps the pending users after a while (activation invitation period) before deleting them definetely. Can you confirm that this isn’t a bug ?

Thanks.