3rd Party: Microsoft Advertising connectors failing with 'UnexpectedFaultException'

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

We are continuing to monitor all affected connectors after the recent fix deployment and there has been a large reduction so far with only a few accounts still receiving the error from Microsoft.

We will check in with further updates accordingly.

We have deployed the fix for this issue and connectors are recovering with a warning on the dashboard regarding the skipped report.

We will continue to monitor all affected connectors and check in with updates accordingly.

We are currently developing a temporary workaround to skip the problematic reports. We will provide additional updates on its deployment shortly.

The issue is due to a 'ReportingServiceInvalidReportId' error from the source side when querying certain reports. A bug report has been filed with the Microsoft Team and we are awaiting an update from them.

We have identified an issue where Microsoft Advertising connectors are failing with a 'UnexpectedFaultException'. We are currently investigating in more detail and will provide additional updates accordingly.