> For the complete documentation index, see [llms.txt](https://docs.origintrail.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.origintrail.io/for-agents/operate-troubleshoot.md).

# Operate & Troubleshoot

Diagnose the failing layer before changing configuration. Preserve the node home, network, graph, KA, and job identifiers involved.

| Layer         | Check                                                        | Next action                                                                |
| ------------- | ------------------------------------------------------------ | -------------------------------------------------------------------------- |
| Installation  | `dkg doctor --json`, `dkg --version`, running status version | Resolve CLI/daemon skew or wrong home; do not modify unrelated checkouts   |
| Daemon/store  | `dkg status`, `dkg logs`                                     | Verify storage readiness and pressure before retrying a workload           |
| Runtime       | Integration status and discovered tools                      | Restart the intended client/gateway if required; verify again              |
| Identity/auth | `GET /api/agent/identity` with caller credentials            | Confirm the intended agent; never request a remote admin token             |
| Graph scope   | Exact ID, selected view, membership, subscription            | Correct scope; do not broaden access to make a query succeed               |
| Ingestion     | Extraction status and actual quads                           | Distinguish stored artifact from completed semantic extraction             |
| Peers         | `dkg peers`, `dkg peer info <peer-id>`, catch-up status      | Check network, reachability, and subscription                              |
| Share/publish | Existing KA history and job details                          | Follow that operation's retry/ambiguity contract                           |
| Funds         | `dkg wallet` and selected payer/PCA                          | Funding is for on-chain steps, not an explanation for every WM/query error |

Use status and the served skill on the configured endpoint; `127.0.0.1:9200` is only the default. Read-only health inspection should not rotate credentials or restart a healthy node.

**Done:** state the observed cause, the change actually made, and a repeated operation proving recovery. If recovery is blocked, retain the precise error/job evidence and identify the missing prerequisite. Do not claim a successful write or publish because a retry was accepted.


---

# 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.origintrail.io/for-agents/operate-troubleshoot.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.