# Major failure：httpstatus code:401 result:{code=124, message=Invalid access token.}

**URL:** <https://devforum.zoom.us/t/major-failure-httpstatus-code-401-result-code-124-message-invalid-access-token/89171>\
**Category:** API and Webhooks\
**Created:** [May 29, 2023, 6:23am UTC](https://devforum.zoom.us/t/major-failure-httpstatus-code-401-result-code-124-message-invalid-access-token/89171 "2023-05-29T06:23:51Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![kaichen](https://avatars.discourse-cdn.com/v4/letter/k/3da27b/32.png) [@kaichen](https://devforum.zoom.us/u/kaichen)\
**Post date:** [May 29, 2023, 6:23am UTC](https://devforum.zoom.us/t/major-failure-httpstatus-code-401-result-code-124-message-invalid-access-token/89171/1 "2023-05-29T06:23:51Z")

</div>

故障描述：

2023-05-25 14:13:50:152 左右系统更新了新的server-to-server token，详细信息如下：  
accountId：jyhcMSzySBO9uGyXTp0g1A

生成的server-to-server token为：  
eyJzdiI6IjAwMDAwMSIsImFsZyI6IkhTNTEyIiwidiI6IjIuMCIsImtpZCI6IjlmOTUwZjg3LTQ0ZjItNGYwOC05ZWUxLTg4ODNkNDJhZjhjYiJ9.eyJhdWQiOiJodHRwczovL29hdXRoLnpvb20udXMiLCJ1aWQiOiJJdE5iTjVDT1F6S2xnMV9EOXR0Y1d3IiwidmVyIjo5LCJhdWlkIjoiYzIxNjA5YWMyZTg5OTFjZjY2YzE0NDI0OWFkMzczZmQiLCJuYmYiOjE2ODQ5OTUyMjksImNvZGUiOiJMNlVtYmZtWFF1ZW5hS1hqelM1Z2h3SmFNUEc2eTBUOEgiLCJpc3MiOiJ6bTpjaWQ6STdEcE5ndFR6R0RJcEp2WGhrbWhnIiwiZ25vIjowLCJleHAiOjE2ODQ5OTg4MjksInR5cGUiOjMsImlhdCI6MTY4NDk5NTIyOSwiYWlkIjoianloY01TenlTQk85dUd5WFRwMGcxQSJ9.CiUV-e9qwtiTE1tBKc7ob9gfrS0qfdhW-R6Xw-8X2wpZ4NNAW79UVBEJCfZvMDjoenPb3Ek0yc0CM1fEhNFHCg

在2023-05-25 15:00:00左右，发现了大量创建会议失败的问题，报错信息为：httpstatus code:401  
result:{code=124, message=Invalid access token.}。之后紧急切回原来的JWT后解决

以下是zendesk的回复：  
Looking at the email, it shows that you may have been generating 4 tokens every hour which is the cause of the 124 invalid access token errors. If exceed the limit of 3 for generated tokens, it will trigger 124 invalid access token errors.

但是我们查看后台日志，发现并没有在1小时内申请多个token。我们的代码逻辑是1小时生成1个token。  
请帮忙确认故障原因。谢谢。

 ![adf554](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/7/c/7c766c310c8b61ed82d6fa43cfbb57241e37c5b3.png)

---

<div class="post-metadata">

**Author:** ![kaichen](https://avatars.discourse-cdn.com/v4/letter/k/3da27b/32.png) [@kaichen](https://devforum.zoom.us/u/kaichen)\
**Post date:** [May 31, 2023, 5:29am UTC](https://devforum.zoom.us/t/major-failure-httpstatus-code-401-result-code-124-message-invalid-access-token/89171/2 "2023-05-31T05:29:10Z")

</div>

anyone help?It seems a bug for server to server token?  
thank you…

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [May 31, 2023, 1:33pm UTC](https://devforum.zoom.us/t/major-failure-httpstatus-code-401-result-code-124-message-invalid-access-token/89171/3 "2023-05-31T13:33:33Z")

</div>

Hi @kaichen  
Thanks for reaching out to us!  
When you are working with Server to Server Oauth apps to generate access tokens, generating a new token, invalidates the previous one, even if that previous token has not expired yet.  
Please, make sure that you are not using an invalid token when calling our APIs.  
Thanks  
Elisa

---

<div class="post-metadata">

**Author:** ![kaichen](https://avatars.discourse-cdn.com/v4/letter/k/3da27b/32.png) [@kaichen](https://devforum.zoom.us/u/kaichen)\
**Post date:** [June 5, 2023, 8:52am UTC](https://devforum.zoom.us/t/major-failure-httpstatus-code-401-result-code-124-message-invalid-access-token/89171/4 "2023-06-05T08:52:00Z")

</div>

Thank you Elisa.  
We checked our code and logic,it did not use the previous token.  
On the other hand,we had transfered to the ‘server to server oauth’ from jwt for about 2 weeks before 2023-05-25 and no code changes happend on 2023-05-25.So the failure was odd.  
Would you please have a look at the log at the error time?We have to know the real reason about this failure before we transfer from jwt to server to server oauth again.  
Thank you for you and your collegues’ help!

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [June 7, 2023, 1:39pm UTC](https://devforum.zoom.us/t/major-failure-httpstatus-code-401-result-code-124-message-invalid-access-token/89171/5 "2023-06-07T13:39:05Z")

</div>

Hi @kaichen  
I have sent you a private message. could you reply there please

---

<div class="post-metadata">

**Author:** ![kaichen](https://avatars.discourse-cdn.com/v4/letter/k/3da27b/32.png) [@kaichen](https://devforum.zoom.us/u/kaichen)\
**Post date:** [June 8, 2023, 5:54am UTC](https://devforum.zoom.us/t/major-failure-httpstatus-code-401-result-code-124-message-invalid-access-token/89171/6 "2023-06-08T05:54:05Z")

</div>

thank you .let me have a look.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [June 10, 2024, 9:30pm UTC](https://devforum.zoom.us/t/major-failure-httpstatus-code-401-result-code-124-message-invalid-access-token/89171/7 "2024-06-10T21:30:27Z")

</div>

This topic was automatically closed 368 days after the last reply. New replies are no longer allowed.
