ERROR CODE
TVO-OP-035: An interrupted lane change cannot be reconciled
An interrupted lane change cannot be reconciled. This page shows why it happens and how to fix it.
Last updated September 22, 2026
If this error reveals a permission or cryptography flaw, do not post it — follow coordinated disclosure. Do not report security vulnerabilities here. This board is public and operated by a third-party vendor. Read https://tovio.dev/security and use the private channel it names. Never paste repository contents, file paths, diffs, tokens, keys, or other people's data — describe the behaviour instead.
Why it happened
In the catalog's worked example, TOVIO explains it like this. Names and values in it are illustrative.
A lane create or delete was interrupted, and since then its lane, operation log or audit head changed to a value the journal neither started from nor intended. TOVIO kept the journal and changed nothing.
How to fix it
- Inspect the repository and its signed audit chain (read-only, runs while the change is pending):
tovio fsck - Publish the interrupted change's pre-signed audit record if only local history moved:
tovio fsck --repair - If repair refuses, the lane or audit head was changed outside TOVIO: restore .tovio from a backup, or move .tovio/lane-mutation.vex out of the repository to accept the lane as it is, with no lifecycle record
What to read
- Error reference — the three-part message standard (what happened, why, what to do next), the exit-code classes, the
--jsonshape, and the everyday codes. It is a curated subset, so it may not name this one:TVO-OP-035is in theOParea and carries the same three-part message either way. - Troubleshooting — the diagnostic commands and recovery paths behind the most common failures.
Still stuck, or is the message wrong?
Report it. The link carries only this code and the surface; describe the behaviour in your own words and never paste secrets, capability tokens, session strings, or private repository data.