Our team is encountering an issue where calling the /chat/users/me/messages endpoint with pagination and a certain page_size will initially work, but errors after a couple of requests. The initial next_page_tokens work, but eventually a request with the next token will result in a 400 bad request, with error code: -1 and message: null.
We have already established that the issue is not with the page_size or the bearer token, as the issue is encountered regardless of page size, and the token is not expired and can be used in requests after the faulty one.
Looking online and in this forum, we cannot find anyone else encountering this issue. Does anyone have any idea what this issue might be? We can provide more technical information if necessary.
Additional information. We have done a lot of tests and were able to pinpoint the problem to the following:
Within some of the channels we are trying to read, there are “Zoom notes” shared (the link to a Zoom note). And it seems that in some cases we’re not able to read messages when they contain a shared Zoom note not created by the account that we use to read the channel messages.
All other types of messages will be returned, but when a page contains one more more messages with a Zoom note it will result in the following error message:
{
"code": -1,
"message": null
}
Some specs for the Zoom team (when reading with us):
Channel “fc8b80c51a2645248c57de99bae2ea6a” has a Zoom note attachment on 21th of August 2024
Channel “927f7f1a6c2b4fd3b95e056abf53911c” has a Zoom note link on 30th of September 2024
In another test channel “ea197604395743c7b2c217ad3c919191” we shared a note created by our own account and those messages are fetchable through the API.
Reading messages (paginated) until the mentioned dates give back correct responses, but on the page containing that message it will result in the -1 error code.
We’ve tested with page sizes of 50, 10 and 5 (the smaller the page size the more succesfull request we were able to do, but all fail when reaching a date where there is a Zoom note link in the chat channel).
The account the we use is member (even Owner) of all the mentioned channels. But we are often not the owner/co-author of the Zoom Note shared in the chat.
Expected behaviour: being able to fetch all pages without an error, and if there is a reason for not passing through links for items that the user doesn’t have access to then: A) ignore them or B) just pass the link (that our user wouldn’t be able to open if we don’t have the correct rights).
Indeed it seems be tied into the shared “Zoom Notes” links in a channel.
From one of the channels (“927f7f1a6c2b4fd3b95e056abf53911c”) we were allowed to remove the single Zoom Note Link in that channel. Afterwards we were able to read all messages.
After posting the Zoom Note link again by ourselves we’re still able to read all messages. So it seems that there is something with Zoom Note links that are shared by other users.
Through the app we have access to these channels, messages and links (we can even open the Zoom Notes because they are shared with the group that they are posted in). We only get the -1 code error while retrieving through the API.
We’ve also asked on the of authors of the notes to make us co-author and even co-owner of the note, but this didn’t change anything.
So issue still occurres in the channel "fc8b80c51a2645248c57de99bae2ea6a"m, but no longer in “927f7f1a6c2b4fd3b95e056abf53911c”.
Hi @gianni.zoom and @elisa.zoom, sorry to ping you for some attention I saw you are the most active Zoom-employee users on this board.
We’re currently experience some strange behaviour in the messages endpoint that we were able to pinpoint to a specific reproducable case. Because of the resulting -1 error (unknown) during the reading of paginated messages we are not able to continu and/or workaround this issue.
The first post was somewhat vague, but the two replies following our initial post really explain the issue well.
Hoping to hear from you soon! Kinds regards from The Netherlands
Hi @gp_includi_hrmnzr
Thanks for reaching out and for such a detailed message.
I see the issue you are having, as I cannot replicate this myself, I will DM you for some additional information so I can open a support ticket on your behalf so they can report this issue to our Engineering team.
Thanks a lot for your patience!
Hi @gp_includi_hrmnzr
Thank you for reporting this issue! Our team identified this as a bug and it was fixed over the weekend.
Could you please try again and confirm that you are no longer getting this pagination error?
I saw you are the most active Zoom-employee users on this board.