[ROLLBACK OF] Modified logic for calculating Failed Records % could result in new Sync Alert emails

What to do

• Check whether your product depends on Census. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2024-07-18 22:22 UTC and 2024-07-18 22:22 UTC may need a replay.

• Subscribe to Census's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=census works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Census 1

1. resolvedJul 18, 2024, 10:22 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.