Changes / Census / Some syncs failing with "Missing corresponding dataset file for prefix: record_deletes.0"
Census: Major incident: Some syncs failing with "Missing corresponding dataset file for prefix: record_deletes.0"
Summary
Census reported a major Sync Engine incident starting 2025-02-05 22:38 UTC: some syncs failed with "Missing corresponding dataset file for prefix: record_deletes.0" after a code change introduced a bug. A revert deployed at 22:56 UTC; the incident was resolved at 2025-02-05 23:30 UTC after over 30 minutes without errors, with a computed duration of 51 min.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Some syncs failing with "Missing corresponding dataset file for prefix: record_deletes.0"
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2025-02-05 22:38 UTC
Before: not present
After: 2025-02-05 23:30 UTC
Before: not present
After: Sync Engine
Before: not present
After: A recent code change introduced a bug resulting in some syncs failing with the message "Missing corresponding dataset file for prefix: record_deletes.0".
We have identified the problematic change, and a revert is in progress.
Before: not present
After: The revert has deployed. We are monitoring to ensure that the errors subside.
Before: not present
After: No errors have been seen for over 30 minutes. We are declaring the incident resolved.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Some syncs failing with "Missing corresponding dataset file for prefix: record_deletes.0" (this change) Census reported a major Sync Engine incident starting 2025-02-05 22:38 UTC: some syncs failed with "Missing corresponding dataset file for prefix: record_deletes.0" after a code change introduced a bug. A revert deployed at 22:56 UTC; the incident was resolved at 2025-02-05 23:30 UTC after over 30 minutes without errors, with a computed duration of 51 min. | Major incident |