Clay incident

Legacy Audience Ads (beta) syncs are under-exporting audience members

Minor Resolved View vendor source →

Clay experienced a minor incident on July 29, 2026 affecting Clay service, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jul 29, 2026, 06:11 PM UTC
Resolved
Jul 29, 2026, 06:11 PM UTC
Duration
—
Detected by Pingoru
Jul 29, 2026, 06:11 PM UTC

Affected components

Clay service

Update timeline

  1. identified Jul 28, 2026, 05:41 PM UTC

    We're investigating an issue where Legacy Audience Ad syncs (beta) since Friday 7/24 with a NOT filter on the segment are under-exporting rows. We've identified the root cause and are working on deploying a fix.

  2. identified Jul 28, 2026, 09:05 PM UTC

    We're investigating an issue where Legacy Audience Ad syncs (beta) since Friday 7/24 with a NOT filter on the segment are under-exporting rows. We've identified the root cause and are working on deploying a fix.

  3. resolved Jul 29, 2026, 06:11 PM UTC

    We've pushed a fix. We've re-synced all recurring v2 Ad Syncs to re-trigger ad platform syncs with the fixed data. Legacy ad syncs will repair themselves on their next scheduled sync.