Census: [ROLLBACK OF] Modified logic for calculating Failed Records % could result in new Sync Alert emails
Timeline of updates
- resolved
This change has been rolled back to reduce noisy alerts for existing customers. Any alerts that were opened yesterday due to this change have been closed. Recovery emails will not be sent for the alerts opened yesterday.
Failed record alerts will be triggered with the old logic moving forward.
------------Original Update--------------------------
To improve accuracy, we recently updated the calculation that powers the Failed Records % Sync Alert. This one-time correction could result in new alerts to those syncs where the correction applies.The new logic calculates the percent of failed records based on the number of changed records in a sync run, rather than the total number of records in the source.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
8b8d9fb5c9695a84…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Census, started 2024-07-18 22:22 UTC, resolved after 0 min, 1 update(s).
- Title
- [ROLLBACK OF] Modified logic for calculating Failed Records % could result in new Sync Alert emails
- Vendor
- Census
- Date
- URL
- https://rewindex.com/company/census/incidents/tpzlyy8d74s9
Census profileRecent Census incidentsAll outages on July 18, 2024Census in July 2024MarkdownJSON