> For the complete documentation index, see [llms.txt](https://privacyoncoil.gitbook.io/coil-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://privacyoncoil.gitbook.io/coil-docs/developers-and-support/troubleshooting.md). # Troubleshooting Common issues and what to check first. #### A shield is confirmed, but the private balance has not appeared Check the network, wallet synchronization state and transaction status. Confirm that the wallet being viewed is the intended recipient. If assurance conditions apply, inspect those separately from blockchain confirmation. #### A proof is taking longer than expected Check whether the application is still working, whether the device has sufficient resources and whether synchronization is complete. Avoid repeatedly creating new transactions while the original operation's status is uncertain. #### A broadcaster quote is unavailable Check connectivity and the application's supported broadcaster options. An unavailable quote is not evidence that the underlying assets are lost. #### An unshield has not arrived Use the transaction hash to establish whether the transaction was submitted, pending, reverted or confirmed. Confirm the receiving network and token contract. #### Support asks for a recovery phrase Do not provide it. A recovery phrase is not a diagnostic tool. Support should be able to begin with public transaction information and non-sensitive application details. --- # 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://privacyoncoil.gitbook.io/coil-docs/developers-and-support/troubleshooting.md?ask=&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.