Troubleshooting slow sync and Access Token failure in custom Zoom API connector

Slack Knowledge Base Q&A Connector Development
, , , ,
1

Summary

User is experiencing slow sync and Access Token failure midway through when using a custom connector for the Zoom API. They are seeking advice on how to troubleshoot the slowness and resolve the Access Token issue.


Question

Hey team,
I’m building a custom connector for the Zoom API because the community based one doesn’t pull all the data I need.
I’ve got it working just fine with my tests, pulling the data I want through, but when I turn the sync on it takes so long that the Access Token actually fails midway through.

How can I go about figuring out what’s causing something to be so slow? The logs are pretty difficult to read / understand?
Alternatively, does anyone have any tips on how to resolve this?


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["custom-connector", "zoom-api", "slow-sync", "access-token-failure", "troubleshooting"]
2

Hey William,

Zoom access tokens expire in 1 hour:
> Access tokens are valid for one hour from the time they are issued. When an access token expires, request a new one <OAuth for user authorized apps the refresh token> sent with the initial authorization.
Source: https://developers.zoom.us/docs/integrations/oauth/

So I guess the way to go is to switch to the OAuth flow instead. I saw that Airbyte Builder supports this Authentication method.

Also, you can try to use a query param like from to narrow down the amount of data for syncing - let’s say try to pull out the data for last week and see how it goes.