Troubleshooting
Find what you're seeing below. Each page lists the causes, most frequent first, and how to fix them.
Have a quick question instead? See the frequently asked questions.
Read the error first
Every error has a code and a message. In a terminal, Devolutions CLI writes them on one line, for example:
confirmationRequired: Pass --yes to delete the entry.The code is stable, so it's what you search for in this documentation or test in a script. With --output json, the error comes as a JSON document instead, with the code and message in its errors list. See Read results as JSON.
The exit code also tells you what kind of problem it is:
2
The command line was refused before anything happened: a typo, a missing option, or a change without --yes.
1
The command ran but failed, for example because the selected workspace doesn't support it.
3
The background process or the workspace couldn't complete the request.
4
A vault, entry, user, or group wasn't found.
130
You interrupted the command.
The complete list is in Exit codes and errors.
Still stuck?
Collect diagnostics and contact Devolutions support.
Last updated
Was this helpful?