-
Notifications
You must be signed in to change notification settings - Fork 4.9k
fix(source-linkedin-ads): Slightly reduce API budget due to retried 429s #69115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. Helpful Resources
PR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
|
| |:-----------|:-----------|:---------------------------------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ||
| | 5.6.0-rc.1 | 2025-10-29 | [68614](https://github.com/airbytehq/airbyte/pull/68614) | Upgrade to latest CDK to only include the selected columns of the schema in API requests for ad analytics streams | | ||
| | 5.5.5 | 2025-10-27 | [68626](https://github.com/airbytehq/airbyte/pull/68626) | Increase concurrency and introduce initial attempt at API budget | | ||
| | 5.6.1 | 2025-11-04 | [tbd](https://github.com/airbytehq/airbyte/pull/tbd) | Reduce the API budget to cut down on the number of 429s and retries | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚫 [vale] reported by reviewdog 🐶
[Google.Units] Put a nonbreaking space between the number and the unit in '429s'.
|
|
Deploy preview for airbyte-docs ready! ✅ Preview Built with commit e19f2cc. |
On the LinkedIn Ads Developer portal we're seeing some elevated counts of 429 errors. We should tune the budget a little lower because having the connector exponentially backoff on rate limit errors is slower than if we proactively limit at a lower rate and this still might allow us to increase the concurrency level further due to the better tuned proactive rate limits