Data Sync - Operational
Data Sync
WebApp - Operational
WebApp
Notifications - Operational
Notifications
Normalization - Operational
Normalization
Airbyte Homepage (Airbyte.com) - Operational
Airbyte Homepage (Airbyte.com)
Third Party Component - Operational
Third Party Component
Airbyte API - Operational
Airbyte API
Connector Builder - Operational
Connector Builder
Airbyte Agents - Operational
Airbyte Agents
Notice history
View current statusMay 2024
- Resolved · UTC
This incident has been resolved.
As a reminder, this fix is a breaking change. This requires an upgrade to the new 3.1.0 version of Facebook Marketing. Please follow the steps here to successfully update the connector.
- Monitoring · UTC
The team has provided a fix which is a breaking change. This requires an upgrade to the new version 3.1.0 of Facebook Marketing. Please follow the steps here to successfully update the connector.
- Identified · UTC
We are continuing to work on a fix for this incident. Meta Appears to have silently modified the schema of the
AdsInsightsendpoint forconversion_lead_rateandcost_per_conversion_leadcausing the following error message:"error": { "message": "(#100) Tried accessing nonexisting field (cost_per_conversion_lead) on node type (AdsInsights)", - Investigating · UTC
We are currently investigating this incident. Meta Appears to have silently modified the schema of the
AdsInsightsendpoint forconversion_lead_rateandcost_per_conversion_leadcausing the following error message:"error": { "message": "(#100) Tried accessing nonexisting field (cost_per_conversion_lead) on node type (AdsInsights)",
- Resolved · UTC
This incident has been resolved. If your connection was actively running a sync before 4:00 PM ET/1:00 PM PT, please cancel the sync and start a new one.
- Monitoring · UTC
We implemented a fix and are currently monitoring the result. If your connection was actively running a sync before 4:00 PM ET/1:00 PM PT, please cancel the sync and start a new one.
- Identified · UTC
We have identified the root cause of this issue and are actively investigating the fix. This issue is impacting Users who have updated their Redshift to version 1.0.67305 (https://docs.aws.amazon.com/redshift/latest/mgmt/cluster-versions.html#cluster-version-181)
Apr 2024
- Resolved · UTC
This incident has been resolved. All impacted users should now be able to update source schema to use a healthy Primary Key and return syncs to a healthy state.
- Identified · UTC
We are continuing to see issues while processing complex primary keys(array/JSON type) that are output by Linked In Ads for users syncing to destination BigQuery. We are continuing to work on a fix for this incident.
- Monitoring · UTC
We implemented a fix and are currently monitoring the result. This fix is a breaking change and will require a reset on your connection. More information here.
- Identified · UTC
There are issues with processing complex primary keys(array/JSON type) that are output by Linked In Ads for users syncing to destination BigQuery. We are continuing to work on a fix for this incident.
- Investigating · UTCWe are currently investigating this incident.
