Skip to main content
The run started with no state at the configured path, so it would restart the producer’s change sequence at zero. If that namespace has already published, BigQuery discards the republished lower numbers as stale and every affected row freezes at its old value — with no error on either side. That is why recovery from lost state is not a restart. Fix — to bootstrap a namespace that has never published, set allowColdStart: true. To recover a namespace whose state was lost, publish under a fresh namespace and re-bootstrap every destination; restoring the state file from a backup reintroduces the same failure.

Related topics

Error referenceChangelog