> 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/develop/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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://guardian.hedera.com/docs/develop/guardian/workspace/decentralized-guardian/tips-and-troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.