> ## Documentation Index
> Fetch the complete documentation index at: https://platform.atlan.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on Atlan objects, use the Atlan MCP server at https://api.atlan.com/mcp or the atlanai CLI; `atlanai --map json` prints its command map. Run a read-only identity check before any write.
> The docs MCP server at /mcp searches these docs only. It cannot read or change Atlan objects.
> SDK packages: Python `atlanai` (PyPI) and TypeScript `@atlanai/sdk` (npm). Show Python first, then TypeScript.

# Registry operation errors

> Errors from atlanai search, harness list, harness get, and harness delete commands.

Errors from `search`, `harness list`, `harness get`, and `harness delete`. Run `atlanai context show` before investigating. Workspace context mismatches are the most common cause.

## `search` returns fewer results than the server total

The visible result count is lower than the total reported by the server.

### Cause

Access filtering applies after the server counts matching artifacts. The server total includes artifacts the account cannot access, so the visible set is smaller.

### Solution

The results shown are all artifacts your account can access.

1. Request broader access from your workspace administrator if specific artifacts are missing.

***

## `harness list` returns results from the wrong workspace

The listing shows harnesses from a workspace other than the one intended.

### Cause

The active workspace context points to a different workspace than intended. Commands that default to the active context use it without prompting.

### Solution

Correct the workspace context before rerunning the command.

1. Run `atlanai context show` to confirm the active workspace.
2. Switch with `atlanai context use`, or pass `--workspace <id>` explicitly.
3. Rerun `harness list`.

***

## `harness delete` targets the wrong harness

The archive command runs against a harness that was not the intended target.

### Cause

The wrong harness ID was passed to the command. Harness IDs can look similar across workspaces.

### Solution

Confirm the harness before archiving.

1. Run `atlanai harness get harness_123` to confirm the name and workspace.
2. Verify this is the intended harness before proceeding.
3. Run `harness delete` only after confirming the correct ID. Archiving cannot be reversed through the CLI.

## See also

* [Inspect Registry](/tools/cli/how-tos/registry): Find workspaces and inspect agents, harnesses, and other artifacts.
* [Run diagnostics](/tools/cli/troubleshooting/diagnostics): Inspect installation, daemon logs, and authentication state.

## Need help

If you need assistance after trying these steps, contact Atlan support.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.