Fix an error

For feature teams. This page helps when a joomiz command fails. Start with the exit code. Then read the message.

Read the exit code

A command that fails prints a line that starts with error:. The exit code says what kind of failure it was.

Code	Meaning	What to do
`0`	The command worked.	Nothing.
`1`	The control plane found problems in your file, or it refused the call.	Read the message.
`2`	The command cannot start: a missing option, an unknown command or no credential.	Fix the command.
`3`	The control plane gave no usable answer.	Check the address. Run the command again.
`4`	`joomiz runs show` only: the run is not final yet.	Wait, and ask again.
`5`	`joomiz plan --strict` only: the plan is incomplete.	Plan again, or ask your platform team.

When two codes apply, 3 comes first, then 1, then 5.

Exit code 1

The control plane found a problem. The sections below show the refusals that people meet most often.

Exit code 2

The command did not start. For example, no credential is available:

error: no credential is available. Run 'joomiz login', or ... for a non-interactive caller.

The line ... marks words that this page cuts.

A missing option shows the usage of the command and exits with 2. An unknown command gives a hint:

Unmatched argument at index 0: 'deploy'
Did you mean: joomiz plan or joomiz login?

Exit code 3

The CLI could not get an answer, for example because the control plane is not reachable. The file was not checked, and nothing was changed. The address in the message is replaced, as in the other outputs:

error: the request to https://joomiz.example.com/validate could not be completed: the connection was refused
  the file was not checked; re-run the command to try again

A plan or an apply that takes too long ends with the same code. The message names the run, so that you can look at it with joomiz runs show.

Exit code 4

joomiz runs show says that a run is still working. Read your runs shows the output.

Exit code 5

joomiz plan --strict found that the drift check was incomplete. Preview a change shows the output.

Refusals that a feature team meets

A call that the control plane stops before any work is a refused call. Each one has a reason. This table shows the reasons that you can fix yourself.

Message	What it means	Fix
`Application not found`	The application is not registered.	Run `joomiz register`.
`Not your application`	The application belongs to another team.	Sign in with the sign-in of the owner team.
`Unsupported joomiz.yaml version`	The file has a version that the control plane does not know.	Write `version: 1`.
`the control plane found ... problems`	The file did not pass the checks.	Run `joomiz validate`, and fix the problems.
`No provisioner registered`	No provisioner handles a type of your file.	Tell your platform team the type.
`No appliable plan`	The file was never planned.	Run `plan`, then `apply`, with the same file.
`Apply already in progress`	Another apply holds the lock.	Follow the run in the message. Apply again after it ends.
`Stale plan`	The environment changed after your plan.	Plan again, then apply.

Run results, refusal reasons and exit codes lists every reason.

Read a validate error

A message from joomiz validate names the environment, the entry and the part of the entry. Check your file shows how to read it. Point one value at another lists the errors of references.

Find the run

Every plan and apply is a run, also a refused call. List the refused runs:

joomiz runs --status refused

You see:

ID                                    KIND   APPLICATION                  ENVIRONMENT  STATUS                             STARTED
ecbbea7a-783a-414b-821e-fd038425b2a1  apply  container-shop (4a2a1cc8)    test         refused (no_appliable_plan)        2026-10-28T16:22:51.581Z
8980e7d0-1d63-4423-a871-750fd8bd9e84  plan   container-shop (4a2a1cc8)    test         refused (unclaimed_resource_type)  2026-10-28T16:22:51.043Z
9010846c-40e0-4991-9a0b-4d6049a54ccc  plan   quick-start-shop (f86f491d)  test         refused (invalid_submission)       2026-10-28T16:22:49.925Z
74dc1e58-8abd-40e7-b5c4-e3bc17c43c0e  plan   reference-shop (48908c60)    test         refused (unsupported_version)      2026-10-28T16:22:48.859Z
3fb7ef00-f6d9-453e-83ca-97b3dde17241  apply  reference-shop (48908c60)    test         refused (stale_plan)               2026-10-28T16:22:27.955Z
c383ac6b-d5d8-4422-b93f-7c50e0c04dc2  apply  reference-shop (48908c60)    test         refused (apply_in_progress)        2026-10-28T16:20:37.140Z
2c0bb399-450b-4668-b3c7-28d5e15d648a  plan   quick-start-shop (f86f491d)  test         refused (application_not_found)    2026-10-28T16:19:18.321Z

The reason is in parentheses after refused. joomiz runs show <id> prints the run. Read your runs explains the output.

Ask your platform team

Ask your platform team when the message is not about your file. For example, a provisioner failed, or no provisioner handles a type. Send these things:

The full text of the error message.
The command that you ran, and the name of the environment.
The ID of the run, from joomiz runs.
The time of the call.

Learn how to sign in, and which role you need, in Sign in and get access.