> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/3.7.0/guardian/workspace/decentralized-guardian/tips-and-troubleshooting.md).

# Tips and Troubleshooting

* Save the public link and the generated access key in a local file before moving on. You will need both when importing the key into the remote user.
* If nothing seems to happen after an action, check the Incoming Requests screen. A pending, unapproved request blocks the next step of the workflow.
* Give each action time to process. **Actions** move from **New** to **Completed** as the event is synchronized; operating before processing finishes is the most common source of confusion.
* Remember the approval chain: the policy must be published as Public, the dependent standard registry must approve the imported policy, and each workflow action must be approved in Incoming Requests by the user sending the operation.
* Verify the remote user after creating it. Its Hedera account ID, user topic, and DID must match the dependent user's profile exactly.


---

# 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://guardian.hedera.com/docs/3.7.0/guardian/workspace/decentralized-guardian/tips-and-troubleshooting.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.
