ERROR CODE
TVO-FLOW-006: Coordinated merge-back refused; nothing advanced
Coordinated merge-back refused; nothing advanced. This page shows what TOVIO prints.
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.
What TOVIO prints
The catalog's example of what TOVIO prints for this code in a terminal. Names, paths and counts in it are illustrative.
✗ Cannot land: the coordinated merge-back cannot complete, so nothing was landed
Workflow `com.tovio.gitflow@1` requires `release/2.4` to land onto both:
main would land cleanly
develop blocked: 2 unresolved conflicts
Every target is gated before any lane advances — no ref was moved.
Resolve the blocked target, then land again:
tovio status --conflicts
See where the lanes stand:
tovio health
[TVO-FLOW-006]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-FLOW-006is in theFLOWarea 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.