Syncs for Data Lake Destinations Are Failing With Table Corruption Error

We have resolved this incident.

A fix has been implemented and we are monitoring the results.

If you have Connection failures due to the "data_lake_corrupted" task, please raise a Support Ticket for assistance in resolving the issue. Please avoid dropping any tables before contacting support.

Communications have been sent to customers with AWS S3 destinations and communications for other destinations will follow soon.

If you have Connection failures due to the "data_lake_corrupted" task, please raise a Support Ticket for us to assist in resolving this issue.

We will be sending a communication to all affected customers with further details on this issue and the resolution.

Customers with bucket versioning enabled, please raise a Support Ticket for us to provide further guidance on resolving this issue.

Customers with bucket versioning enabled can proceed to restore all files for their bucket to allow the sync to complete successfully. For customers without bucket versioning enabled, our engineering team is actively working on determining the next steps and will provide further guidance shortly

We have identified the root cause of the issue, which was related to orphan file cleanup deleting some active files. A hotfix has been deployed to prevent further impact. We are currently working on unlinking the deleted files to restore sync functionality. Our team continues to actively work on resolving this.

We are continuing to work on a fix for this issue.

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