3rd Party: LinkedIn Ad Analytics Connections are failing with exception "HTTP 307 Temporary Redirect"

This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully.

Incident Summary
Description:
We identified an issue for LinkedIn Ad Analytics which resulted in syncs failing with a "HTTP 307 Temporary Redirect" errors.

Timeline:
This issue began on May 20th at 18:00 UTC and was resolved on May 21st at 18:00 UTC.

Cause:
The LinkedIn API started intermittently responding with 307 errors, leading to sync failures.

Resolution:
Re-tries have been added to the sync logic for endpoints encountering a 307 error and subsequent failures will cause the connector to skip the request, with an associated warning in the dashboard.

We have deployed a fix for this issue: endpoints returning the 307 error will be re-tried, as we found that subsequent requests will succeed. If the endpoint does continue to fail, we will skip the request and present a warning within the dashboard.

We will continue to monitor all affected connectors until they resume their normal sync functionality.

We have identified that the issue is an intermittent error that is occurring on API calls.

We are working on a fix to handle this error with a retry mechanism. We are also engaged with LinkedIn to have them investigate and resolve the occurrences of the error, if possible.

The issue has been identified and we are working to resolve it.