# Last\_client\_version is delayed

**URL:** <https://devforum.zoom.us/t/last-client-version-is-delayed/15460>\
**Category:** API and Webhooks\
**Created:** [April 29, 2020, 5:49pm UTC](https://devforum.zoom.us/t/last-client-version-is-delayed/15460 "2020-04-29T17:49:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![adam.frost](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@adam.frost](https://devforum.zoom.us/u/adam.frost)\
**Post date:** [April 29, 2020, 5:49pm UTC](https://devforum.zoom.us/t/last-client-version-is-delayed/15460/1 "2020-04-29T17:49:36Z")

</div>

**Description**  
last\_client\_version doesn’t seem to be updated frequently

**Error**  
I update my own Zoom client to 5.0 on Monday 4/27/2020. I ran a report today (Wednesday 4/29/2020) in java using the REST API and getting the last\_client\_version object for each user. For my profile, it returns 4.6.20033.0407(win) which was the old version. I am currently running 5.0. I have closed out of Zoom, restarted, and have started meetings as the presenter since I updated to 5.0. Can you tell me how often that object is updated? We are trying to make sure all our users are upgraded to 5.0.

Thanks.

**Which App Type (OAuth / Chatbot / JWT / Webhook)?**  
REST API

**Which Endpoint/s?**  
I start by getting users from the main account:  
[https://api.zoom.us/v2/users](https://api.zoom.us/v2/users)

Then I cycle through the subaccounts and get users from there:  
[https://api.zoom.us/v2/accounts/accountID/users](https://api.zoom.us/v2/accounts/accountID/users)

**How To Reproduce (If applicable)**  
Steps to reproduce the behavior:  
Request a user via REST API and see if the last\_client\_version matches

**Screenshots (If applicable)**  
If applicable, add screenshots to help explain your problem.  
 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/2X/1/1bfc7da56db2cf3bf350ef0f661c28843812f73b.png)

**Additional context**  
One screen shot shows my Zoom console and shows I have 5.0 installed.  
The other screen shot shows the data that exported to Excel from the API and shows version 4.6.20033.0407(win)

Thanks.  
Adam

---

<div class="post-metadata">

**Author:** ![adam.frost](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@adam.frost](https://devforum.zoom.us/u/adam.frost)\
**Post date:** [April 29, 2020, 5:59pm UTC](https://devforum.zoom.us/t/last-client-version-is-delayed/15460/3 "2020-04-29T17:59:41Z")

</div>

This also seems to be the case with the last\_login\_time object in the main User object.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [May 5, 2020, 5:03pm UTC](https://devforum.zoom.us/t/last-client-version-is-delayed/15460/4 "2020-05-05T17:03:50Z")

</div>

Hey @adam.frost,

There is a 3 day buffer for the `last_login_time` and `last_client_version`. You should see it updated now. (ZOOM-131387)

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![adam.frost](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@adam.frost](https://devforum.zoom.us/u/adam.frost)\
**Post date:** [May 5, 2020, 5:24pm UTC](https://devforum.zoom.us/t/last-client-version-is-delayed/15460/5 "2020-05-05T17:24:35Z")

</div>

Hi @tommy, thanks for the reply. Is that standard and there will always be a 3 day buffer? Or is it just for when major new releases happen? Seems a little pointless to have the buffer when we need updated information in real time. Thoughts?

Best,  
Adam

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [May 11, 2020, 7:00pm UTC](https://devforum.zoom.us/t/last-client-version-is-delayed/15460/6 "2020-05-11T19:00:01Z")

</div>

Hey @adam.frost,

Due to our current design it is standard. I will keep you updated on any plans to improve this.

Thanks,  
Tommy
