> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/cli/reference/exit-codes-and-errors.md). # Exit codes and errors Devolutions CLI exit codes, how errors are reported in text and JSON output, and the most common error codes with what to do. Every `devo` command returns an exit code, so a script can tell success from failure. When a command fails, it also reports an error code, a short identifier such as `invalidSecretReference`, and a message. ## Exit codes
CODEMEANING
0The command succeeded.
1The command failed, for example because the workspace refused the operation or doesn't support it.
2The command line is invalid, and nothing was done: unknown command or option, missing or invalid value, options that can't be combined, or a change without --yes.
3The background process couldn't be reached or didn't answer in time, or it reported an error. A local profile that can't run a vault or entry command, for example a vault change (sqliteVaultLifecycleUnavailable), also exits with 3. See The background process won't start.
4An item you asked for wasn't found, such as a workspace, vault, entry, user, or group, or a field with devo secret read and devo secret get. Some commands report a missing item with 1 instead: for example, devo secret get on a local profile returns sqliteSecretNotFound with 1. The Error codes page gives the exit code of each error.
124devo secret run only: the command exceeded --timeout-seconds and was stopped.
130The command was interrupted, for example with Ctrl+C. With devo secret run, the command it started was cancelled.
### `devo secret run` When the command it starts runs to the end, `devo secret run` exits with **that command's exit code**, so your scripts and pipelines see the same result as if they had run the command directly. Exit codes `124` and `130` apply only when the command is stopped. If `devo secret run` can't write the file given with `--receipt-file`, it exits with `1`. Before the command starts, an invalid `--env-file` or a reference that needs a missing environment variable exits with `2`; another failure to read a secret exits with `1`. ## How errors are reported * **Text output** (the default): the error is written as `: `, usually to the error output. Errors of the commands that work only with Devolutions Cloud or Devolutions Server, such as most `devo admin` commands, go to the standard output. For an invalid command line, the help of the command follows. * **JSON or YAML output**: the error goes to the standard output, in the same envelope as a result, with `status` set to `error` and an `errors` list. Each error has a `code` and a `message`. An invalid command line returns the code `usageError`, and `usageSuggestion` when Devolutions CLI has a correction to suggest. See [Read results as JSON](/cli/for-devops-and-administrators/automate/json-output.md). * **`devo secret run`**: whatever the output format, the errors that happen while it reads the secrets or runs the command (timeout, cancellation, standard input) are written as plain `: ` text to the error output. ## Common error codes The table below lists the error codes you'll meet most often. For every error code, see [Error codes](/cli/reference/error-codes.md).
ERROR CODEWHAT IT MEANSWHAT TO DO
usageErrorUnknown command or option, or a missing argument.Check the spelling with devo <command> --help. See Commands.
conflictingOptionsTwo options that can't be used together, such as --json and --yaml, or --quiet and --verbose.Keep one of them. See Global options.
missingParameter, invalidParameterValueA required value is missing, or a value isn't allowed.Read the message: it names the option. Check the allowed values with --help.
invalidSourceThe --source value isn't valid.Use sqlite, cloud[:<context>], or server[:<context>].
confirmationRequired, mutationConfirmationRequiredThe command changes or deletes something and wasn't confirmed.Add --yes once you're sure.
rawSensitiveValueRejectedA secret was passed in a way that could expose it, such as a password as a plain field value.Use devo secret set with --value-env or --value-file. See Update a secret from a script.
invalidSecretReferenceThe reference isn't written correctly.See the messages in Secret reference syntax.
unsupportedSecretAttributeThe ?attribute= value isn't known.Use value, type, id, title, or purpose. otp is accepted in a reference, but no workspace type returns a value for it. See Attributes.
missingSecretReferenceVariableA reference in a template uses an environment variable that isn't set.Set the variable, or give it a default with ${NAME:-default}. See References inside a text.
secretLaunchArgumentReferenceA devo:// reference was written as an argument of the command to run.Pass it with --env-ref, --stdin-reference, or --manifest. See Run a command with its secrets.
secretLaunchTimedOutThe command started by devo secret run exceeded --timeout-seconds.Raise the timeout, or find out why the command takes so long.
secretLaunchCancelled, interruptedThe command was interrupted.Run it again.
operationNotSupportedBySourceThe selected workspace type can't run this command.Select another workspace with --context. See A command says the workspace doesn't support it.
cloudContextNotFoundNo Devolutions Cloud context with that name, or no current one.Check devo context list, or sign in with devo login. See Sign-in fails or the session expired.
daemonUnavailable, daemonTimeout, daemonIoErrorThe background process couldn't be reached, didn't answer in time, or the connection broke.Run devo daemon status, then devo daemon restart. See The background process won't start.
unexpectedErrorAn error Devolutions CLI didn't expect.Run devo doctor and contact support. See Collect diagnostics for support.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.devolutions.net/cli/reference/exit-codes-and-errors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.