Skip to main content
Census

Sync Runs Failing with Undefined Column Error

Degraded Lasted 26m · started · Census's page

Level
confirmed
Worst impact
Degraded
Components
Sync Engine
Down Index
23of 100

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 26m it lasted.

    Anything that failed between 2025-06-06 17:52 UTC and 2025-06-06 18:18 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 2

  1. monitoring

    Some syncs started failing with the following error at 12:18pm (EST) "ActiveRecord::StatementInvalid: PG::UndefinedColumn: ERROR: column sync_configurations.new_diff_timestamp_expression_id does not exist" This was due to a brief issue during a schema update. The problem has been resolved, and we are monitoring.

    provider

  2. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-000cd26320

Is Census still down?

No, this incident was resolved 2025-06-06 18:18 UTC. For Census's live state, see https://down.guide/census.

How long did it last?

26m, from 2025-06-06 17:52 UTC to 2025-06-06 18:18 UTC, by the times Census posted.

What was affected?

Census named Sync Engine.

What caused it?

Census hasn't published a root cause. If it does, it shows here.

Where does this come from?

Census's official status page, https://status.getcensus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.