3rd Party: LinkedIn Ads connectors are failing with a HTTP 400 exception
Incident
Report for Fivetran
Resolved
This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully.
Description:
We identified an issue for LinkedIn Ads which resulted in syncs failing with a "HTTP 400 Bad Request" exception error.
Timeline:
This issue began on January 28 2025 at 08:20 UTC and was resolved on February 3rd 2025 at 11:28 UTC.
Cause:
The Connectors were failing when API requests contained 20 or more fields. The LinkedIn team has identified the issue on their end and is actively working on a resolution.
Resolution:
To mitigate the issue from our side, we have reduced the batch size of the request, limiting it to 17 fields.
Description:
We identified an issue for LinkedIn Ads which resulted in syncs failing with a "HTTP 400 Bad Request" exception error.
Timeline:
This issue began on January 28 2025 at 08:20 UTC and was resolved on February 3rd 2025 at 11:28 UTC.
Cause:
The Connectors were failing when API requests contained 20 or more fields. The LinkedIn team has identified the issue on their end and is actively working on a resolution.
Resolution:
To mitigate the issue from our side, we have reduced the batch size of the request, limiting it to 17 fields.
Monitoring
We deployed a hotfix with a workaround and the connectors are recovering. We are monitoring the connectors.
Update
We are working towards a workaround to fix this issue
Identified
We have identified an issue where some LinkedIn Ads connectors are failing with an HTTP 400 Bad Request exception. LinkedIn has acknowledged this issue with its API. We will continue to work with LinkedIn support on a resolution and provide additional updates.
This incident affected: Marketing connectors (LinkedIn Ad Analytics).