ERROR CODE

TVO-FORGE-099: The Forge is not ready to serve

The Forge is not ready to serve. This page shows what TOVIO prints, 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 condition of serving is unmet; the body names which.

How to fix it

  1. Read failing and fix the named condition (the state root's permissions and space, the HA lease, the replication peers, the billing workers)
  2. During a rollout, wait: readiness turns on when the listeners bind

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, and the command exits with status 1.

✗ The Forge is not ready to serve

  failing: store_root_writable
  Check `storage_dir` — its permissions and free space — and the Forge's log.
  [TVO-FORGE-099]

What to read

  • Error reference — the three-part message standard (what happened, why, what to do next), the exit-code classes, the --json shape, and the everyday codes. It is a curated subset, so it may not name this one: TVO-FORGE-099 is in the FORGE area 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.

Report this error

All error codes