Skip to content
TwinCommitDocs

Broken tables

A table is broken when TwinCommit sees an operation on it that cannot be followed from the log. TwinCommit stops applying changes to that table only. Every other table in the pipeline keeps replicating.

Why tables break

Section titled “Why tables break”

See the list in schema changes. Other causes include a compressed row image the source could not expand, and on PostgreSQL targets a character value that contains a NUL byte.

How you find out

Section titled “How you find out”
  • twincommit status shows the table state as broken with the reason.
  • twincommit_broken_tables rises above 0. Alert on it; see Prometheus metrics.
  • A JSON log line with "level":"error","table":"SCHEMA.TABLE" is written.
  • The MCP get_status tool reports it, and explain_error suggests the fix.

Repair

Section titled “Repair”
Terminal window
twincommit snapshot -config pipeline.yaml -tables SCHEMA.TABLE

Then restart run so it reloads the table definition. If the column layout changed, update the target table first.