Exit Codes
The exit status of every Out Plane CLI command, code by code.
Every command exits with one of these, and 0 means it did what it said. The numbers
are a contract: they are appended to, never reused, and never given a new meaning, so a
script that pinned one against an old release stays correct against a new one.
Each command's page lists the codes that command can actually produce, and
outplane schema publishes the same per command. In a structured format the failure
also arrives as an error object on standard output, carrying the
kind below along with a stable code.
Two of them are worth singling out. 4 is not a failure: a destructive command stopped
and handed back the command that would proceed. And 9 has exactly one remedy, which is
outplane update.
| Exit | Kind | Worth Retrying | Meaning |
|---|---|---|---|
1 | internal | no | An unexpected failure in the CLI itself. |
2 | usage | no | Invalid arguments, unknown flag, or client-side validation failure. |
3 | auth | no | Not authenticated, token revoked or expired, or forbidden for this team. |
4 | confirmation_required | no | A destructive operation stopped. Replay the command in confirm_command. |
5 | not_found | no | The named resource does not exist, or is not visible to this credential. |
6 | conflict | no | The resource already exists, or a concurrent change won. |
7 | quota | no | Plan limit reached or payment required. Not a rate limit; retrying will not help. |
8 | upstream | yes | The Out Plane API returned a server error. |
9 | upgrade_required | no | This release of the CLI is too old for the API. Updating is the only fix. |
124 | timeout | yes | A client-side deadline expired. The server operation may still be running. |
130 | interrupted | no | Cancelled by the user. |