We’ve fully resolved the issue.
Resolved after 3h 3m
We’ve fully resolved the issue and all Claygent workflow nodes should be running as expected.
Resolved after 2d
Earlier today we experienced elevated error rates and increased latency across a small number of workspaces on the Clay application due to a partial outage with our cloud services provider. During this degradation webhook processing was temporarily disabled for all workspaces.
This has now been resolved. Access to affected workspaces and tables has been restored and queued webhooks have processed.
We apologize for any inconvenience caused
Resolved after 5h 28m
We've resolved an issue that was affecting function table links.
Resolved after 0m
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.
Resolved after 1d
Clay is back up and running. Thank you for your patience!
We’ve fully resolved the issue. Thank you for your patience while we worked through it.
Resolved after 1d
Clay was unavailable due to an upstream infrastructure provider outage that also affected several downstream providers, including intermittent SSO login issues. This has been resolved and the app is fully operational. Please re-send webhooks and re-run impacted cells.
Resolved after 5h 35m
We've solved this temporary issue contained to the Meta integration that should resolve for new syncs. We will continue monitoring match rates to ensure they continue recovering over time.
Resolved after 5h 33m
We’ve fully resolved the issue.
Resolved after 1h 17m
We’ve fully resolved the issue.
Resolved after 2d
We’ve fully resolved the issue.
Resolved after 1h 43m
We’ve fully resolved the issue.
Resolved after 3d
We've fully resolved this issue.
During this period, some table views may have failed to load, existing rows may not have updated as expected, and Webhooks may have failed to deliver to their destination tables.
If you believe any data was affected, please reach out to our support team and we'll be happy to help.
Resolved after 5h 57m