Custom Connector to Chartmetric API Rate Limit Issue

[slack-user-airbyte]

Hi there, Rate limiting is a common issue when dealing with APIs. In Airbyte, the most common way to handle rate limits is to implement backoff. This means your connector should gracefully handle rate limits without failing the connector process source. You mentioned that you’ve implemented a Backoff Strategy using “Wait time from header” and “Retry-After”. This is a good approach as it allows the connector to wait before retrying a request based on the value specified in the API response source. However, if you’re still encountering issues, it’s possible that there are other factors to consider when trying to slow down a connector. For instance, a user on the Airbyte forum mentioned that their connector never received a 429 or hit exponential backoff when testing locally, but when run from a locally-hosted Airbyte instance, it hit backoffs regularly source. If you’re still encountering rate limit issues that are not automatically retried successfully, you can create an issue on the Airbyte Github page source. Also, please note that in some cases, like with the LinkedIn Ads connector, after 5 unsuccessful attempts, the connector will stop the sync operation source. I hope this helps! If you have any other questions, feel free to ask.