Error reference
When a command fails, the CLI returns a stable YF_* error code, a numeric
exit code, and a link to this page. Codes never change, so scripts and
agents can branch on them without parsing messages. With --json, the code
appears as error.code in the envelope.
For the number-to-code mapping that CI scripts switch on, see exit codes.
YF_USAGE
Exit code 2. Bad flags, a missing positional argument, or an unknown subcommand.
Run the command with --help to see its arguments and flags. Check for a
typo in the subcommand name.
YF_MISSING_INPUT
Exit code 2. The command needs interactive input but stdin is not a TTY
(for example, running yofix login in CI without a token).
Provide the value non-interactively: pass the relevant flag, set
YOFIX_TOKEN, or pipe the value in. Avoid --no-input unless every value
is supplied another way.
YF_NETWORK
Exit code 3. A TCP error, DNS failure, or timeout while reaching the API.
Check your connection and that the API host is reachable. If you set
--host or YOFIX_HOST, confirm the URL is correct. Retry, since this is
often transient.
YF_AUTH_REQUIRED
Exit code 4. No credentials are available and the command needs them.
Run yofix login, or set YOFIX_TOKEN in CI. Confirm the active host with
yofix whoami. See Authentication.
YF_AUTH_EXPIRED
Exit code 4. The token was rejected by the server (HTTP 401), usually because it expired or was revoked.
Run yofix login again to refresh your session, or generate a fresh token
in Settings → Tokens and update YOFIX_TOKEN.
YF_CONFLICT
Exit code 5. The resource already exists (HTTP 409), for example adding a domain or environment that is already configured.
List the existing resources first (yofix domains list,
yofix environments list) and update instead of re-creating.
YF_NOT_FOUND
Exit code 6. The requested resource does not exist (HTTP 404), for example an unknown deployment or run ID.
Check the ID. Use yofix ls or yofix vrt list to find the correct one.
Confirm you are scoped to the right team and project (yofix whoami,
yofix status).
YF_QUOTA_EXCEEDED
Exit code 7. A plan limit was reached (HTTP 402 / billing).
Review usage with yofix teams usage, then upgrade the plan or wait for
the next billing period. See Pricing and usage.
YF_SERVER
Exit code 8. The API returned a 5xx error.
This is server-side. Retry shortly. If it persists, the requestId in the
JSON envelope helps support trace the failure.
YF_TIMEOUT
Exit code 8. A long-running command (deploy, watch, or
inspect --wait) exceeded its --timeout.
Increase --timeout, or stop waiting and follow progress separately with
yofix logs <deploymentId> --follow. The build itself keeps running.
YF_NOT_IMPLEMENTED
Exit code 9. The feature is scaffolded but waiting on a backend dependency.
Run yofix update to check for a newer CLI. If you are already current,
the capability is not available yet on your instance.
YF_DEPLOY_BUILD_FAILED
Exit code 10. The build finished with a non-zero status.
This is a real build failure, not a CLI problem. Inspect the logs:
yofix logs <deploymentId>Fix the build error and deploy again. See Deploy from your machine.
YF_PROJECT_NOT_LINKED
Exit code 11. .yofix/project.json is missing or incomplete, so the
CLI cannot tell which project you mean.
Run yofix link in the project directory, or pass --project <slug>. The
CLI discovers the link by walking up from the working directory, so run
from inside the linked tree.
YF_INTERRUPTED
Exit code 130. The command received SIGINT or SIGTERM (you pressed Ctrl-C, or CI cancelled the job).
No action needed. Any deployment already queued continues server-side;
reattach with yofix logs <deploymentId> --follow.