ERROR CODE

TVO-FORGE-102: Telemetry is enabled but its [telemetry] table cannot be used

Telemetry is enabled but its [telemetry] table cannot be used. 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.

The [telemetry] table sets enabled = true and one of its fields cannot be used as written.

How to fix it

  1. endpoint must be an https:// origin with no path, query or fragment — the capture path is appended
  2. allow_private_endpoint relaxes the SSRF vet on the ADDRESS; it never permits http://
  3. project_key_ref is the NAME of a keystore entry, never the key itself
  4. heartbeat_secs is 30..=3600; env is 1-32 lowercase letters, digits or dashes
  5. Or set enabled = false to report nowhere, which is the default

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.

✗ Forge telemetry is enabled but cannot be used

  endpoint: http://collector.internal is not https, and the project key travels in the body

  Fix the [telemetry] table in forge.toml, or set enabled = false to report nowhere.

  [TVO-FORGE-102]

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-102 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