Notice history

No notices reported this month

Resolved
June 23, 2026 at 4:49 PM
Resolved
June 23, 2026 at 4:49 PM
Summary:
Meta deprecated the breakdowns=dma (Nielsen DMA) parameter across all Facebook Marketing API versions effective June 22, 2026. This caused failures in the ads_insights_dma and ads_insights_demographics_dma_region streams for the Facebook Marketing source connector.

Resolution:
The connector has been upgraded to v6.0.0, replacing the deprecated DMA streams with Meta’s recommended Comscore Market equivalents. This is a breaking change.

Affected streams:
- ads_insights_dma→ replaced byads_insights_comscore_market
- ads_insights_demographics_dma_region→ replaced byads_insights_demographics_comscore_market_region
Customer action required to resolve:
1. Upgrade the Facebook Marketing source connector to v6.0.0
2. Refresh the source schema to discover the new streams
3. Enable the new Comscore Market streams and reset them to backfill data
4. If using Custom Insights with thedmabreakdown: update the configuration to usecomscore_market instead.
For more information, please see Facebook Marketing Migration Guide.
Identified
June 23, 2026 at 11:32 AM
Identified
June 23, 2026 at 11:32 AM
We are continuing to work on a fix for this incident.
Investigating
June 23, 2026 at 9:37 AM
Investigating
June 23, 2026 at 9:37 AM
We are currently investigating this incident.

Update
June 09, 2026 at 9:00 AM
Update
June 09, 2026 at 9:00 AM
This incident has been resolved. Any connections that failed due to this error should be re-synced and are expected to complete successfully.
Resolved
June 09, 2026 at 12:00 AM
Resolved
June 09, 2026 at 12:00 AM
We identified an issue causing Amazon Seller Partner connections to fail with the error:
Config validation error: None is not of type 'string'

Resolved
May 28, 2026 at 8:15 PM
Resolved
May 28, 2026 at 8:15 PM
This incident has been resolved.
Monitoring
May 28, 2026 at 8:15 PM
Monitoring
May 28, 2026 at 8:15 PM
We implemented a fix and are currently monitoring the result.
Investigating
May 28, 2026 at 7:53 PM
Investigating
May 28, 2026 at 7:53 PM
We are currently investigating this incident.

Resolved
May 15, 2026 at 2:09 AM
Resolved
May 15, 2026 at 2:09 AM
This incident has been resolved.
Identified
May 15, 2026 at 2:02 AM
Identified
May 15, 2026 at 2:02 AM
We are continuing to work on a fix for this incident.
Resolved
May 15, 2026 at 2:00 AM
Resolved
May 15, 2026 at 2:00 AM
This incident has been resolved.
Investigating
May 15, 2026 at 1:00 AM
Investigating
May 15, 2026 at 1:00 AM
We are currently investigating this incident.

Resolved
May 15, 2026 at 12:58 AM
Resolved
May 15, 2026 at 12:58 AM
This incident has been resolved.
Monitoring
May 15, 2026 at 12:55 AM
Monitoring
May 15, 2026 at 12:55 AM
We implemented a fix and are currently monitoring the result.
Investigating
May 15, 2026 at 12:52 AM
Investigating
May 15, 2026 at 12:52 AM
We are currently investigating this incident.

Resolved
May 06, 2026 at 5:34 PM
Resolved
May 06, 2026 at 5:34 PM
This incident has been resolved.
Investigating
May 06, 2026 at 3:55 PM
Investigating
May 06, 2026 at 3:55 PM
Airbyte Agents are unresponsive. The Airbyte Agent SDK and MCP are still working as expected.
We are currently investigating this incident.

Airbyte - Notice history