Sync Trigger Failure

What to do

• Check whether you use Census Sync Engine. 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 5h 48m it lasted.

  Anything that failed between 2026-11-02 15:28 UTC and 2026-11-02 21:16 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.

Root cause

We have identified the issue which has been caused by an internal system certificate update that was not fully applied across all of our older infrastructure.

Category: Certificate expiry

Updates from Census 4

1. investigatingNov 2, 2026, 3:28 PM UTC

   We have identified an issue preventing the triggering of syncs for some users and are currently investigating.

   provider

2. identifiedNov 2, 2026, 4:14 PM UTC

   We have identified the issue which has been caused by an internal system certificate update that was not fully applied across all of our older infrastructure. Because of this, some internal service-to-service communication was interrupted, which prevented reason syncs from being triggered as expected.

   provider

3. monitoringNov 2, 2026, 4:19 PM UTC

   The system certificate has been updated now and it should resolve the sync trigger issue. We are currently monitoring the sync trigger run.

   provider

4. resolvedNov 2, 2026, 9:16 PM UTC

   Issue has been resolved now and sync trigger run are working fine now as expected.

   provider

Corrections

None so far.

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