> 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/help/troubleshooting/not-supported.md).

# A command says the workspace doesn't support it

A Devolutions CLI command says the workspace doesn't support it: check which workspace is selected, and run the command on the right one.

A command stops with `operationNotSupportedBySource`, or another code that says the workspace can't do it, for example:

```
operationNotSupportedBySource: 'devo admin invitation list' is not available for Devolutions Server workspaces; select a Devolutions Cloud context with --context <name>.
```

Devolutions CLI uses the same commands for Devolutions Cloud, Devolutions Server, and local Devolutions Remote Desktop Manager profiles, but each workspace type offers different features. When the selected workspace can't do something, the command says so and changes nothing:

* On Devolutions Cloud and Devolutions Server, and for a command that belongs to one workspace type, the error is `operationNotSupportedBySource` and the exit code is `1`.
* On a local profile, a change the profile can't make is refused with its own error code, such as `sqliteVaultLifecycleUnavailable`, and a message that explains why. The exit code is `3`.

## Why it happens

* The command ran on another workspace than the one you meant, because of the current context, `--context`, `--source`, or an environment variable.
* The command, or one of its options, belongs to one workspace type only.
* The workspace type doesn't offer that change from Devolutions CLI.
* On a local profile, the profile itself doesn't allow the change.

## Fix it

{% stepper %}
{% step %}

### Check which workspace is selected

```bash
devo status
```

The output shows the context and its kind. If it's not the workspace you meant:

* Run the command on the right one: add `--context <context-name>`.
* Or make it the current context: `devo context use <context-name>`.

`--source` and the `DEVO_RDM_SOURCE` and `DEVO_CONTEXT` environment variables also select the workspace, and `--source` overrides `--context`. If the selection surprises you, check whether one of them is set in your terminal or pipeline. See [Switch between workspaces](/cli/guides/connect/switch-workspaces.md) and [Environment variables](/cli/reference/environment-variables.md).
{% endstep %}

{% step %}

### Check which workspace type the command is for

The help of a command often names the workspace type it's for, for example "Devolutions Cloud: inspect and administer user invitations.":

```bash
devo admin invitation --help
```

Options can be limited too. For example, with `devo admin user update`, `--locale` is for Devolutions Cloud only and `--first-name` for Devolutions Server only. Passing one on the other type stops with `operationNotSupportedBySource` and names the option.

The help doesn't always say it, so rely on the [command reference](/cli/reference/commands.md), which lists the workspace types of every command. The guides list the tasks by workspace type:

* [Manage vaults and entries](/cli/for-devops-and-administrators/manage/vaults-and-entries.md)
* [Manage users, groups, and access](/cli/for-devops-and-administrators/manage/users-and-access.md)
* [Review activity logs](/cli/for-devops-and-administrators/manage/logs.md)
  {% endstep %}

{% step %}

### See what the workspace supports

```bash
devo doctor
```

When the background process is running, the `Operations supported by this workspace` line lists what the selected workspace accepts. If `devo doctor` says no background process is running, run any command on the workspace first, such as `devo vault list`, then run `devo doctor` again. To see which secret fields each workspace type can read and write, run `devo secret capabilities`.
{% endstep %}

{% step %}

### Do it another way

If the workspace type doesn't offer the change from Devolutions CLI, make it in the workspace itself: in Devolutions Remote Desktop Manager for a local profile, or in the web interface of Devolutions Cloud or Devolutions Server.
{% endstep %}
{% endstepper %}

## Common cases

<table><thead><tr><th width="300">WHAT YOU TRIED</th><th>WHERE IT WORKS</th></tr></thead><tbody><tr><td><code>devo entry create</code></td><td>Local profile, RDP entries only.</td></tr><tr><td><code>devo entry move</code>, <code>devo entry folder rename</code>, <code>devo entry status set</code>, <code>devo entry tag set</code></td><td>Local profile.</td></tr><tr><td><code>devo entry update</code> on Devolutions Cloud</td><td>Not available. Change the password with <code>devo secret set</code>.</td></tr><tr><td><code>devo vault create</code>, <code>update</code>, <code>delete</code></td><td>Devolutions Cloud and Devolutions Server.</td></tr><tr><td><code>devo admin group create</code>, <code>update</code>, <code>delete</code>, <code>members add</code></td><td>Devolutions Cloud.</td></tr><tr><td><code>devo vault access grant</code>, <code>revoke</code></td><td>Devolutions Cloud.</td></tr><tr><td><code>devo admin logs export</code>, <code>devo entry logs</code></td><td>Local profile.</td></tr><tr><td><code>devo info</code></td><td>Devolutions Cloud and Devolutions Server.</td></tr><tr><td><code>devo entry list --smart-folder</code></td><td>Not available on any workspace type: the command stops with <code>smartFolderUnavailable</code>. Filter with <code>--group</code> or <code>--type</code> instead.</td></tr></tbody></table>

## Still stuck?

If the command should work on your workspace type and still refuses, [collect diagnostics](/cli/help/troubleshooting/collect-diagnostics.md) and contact [Devolutions support](https://devolutions.net/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/help/troubleshooting/not-supported.md?ask=<question>&goal=<user_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.