Fivetran incident

3rd Party: Some Criteo Connections are failing with 'Failed to Upsert Additional Attributes for Creative' Error

Minor Resolved View vendor source →

Fivetran experienced a minor incident on March 10, 2026 affecting Criteo, lasting 3h 35m. The incident has been resolved; the full update timeline is below.

Started
Mar 10, 2026, 06:25 PM UTC
Resolved
Mar 10, 2026, 10:01 PM UTC
Duration
3h 35m
Detected by Pingoru
Mar 10, 2026, 06:25 PM UTC

Affected components

Criteo

Update timeline

  1. identified Mar 10, 2026, 06:25 PM UTC

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

  2. identified Mar 10, 2026, 08:15 PM UTC

    Connector syncs are currently failing due to an unknown creative type format returned by the source API. Our team is actively working on a hotfix to treat this as a warning instead of causing sync failures. We will share another update once the fix has been deployed.

  3. resolved Mar 10, 2026, 10:01 PM UTC

    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 impacting Criteo connections, which resulted in syncs failing with the following error: "Failed to upsert additional attributes for creative" Timeline: This issue began on 2026-03-10 at 15:15 UTC and was resolved on 2026-03-10 at 21:12 UTC. Cause: The issue occurred when the source returned "unknown" attribute types for certain creatives, resulting in sync failures. Resolution: A fix has been implemented to skip the problematic attribute types.