> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/workflows/bulk-remediation/apply-a-bulk-action/troubleshooting.md). # Troubleshooting Some common errors when remediating assets in bulk include: * **Misconfigured workflow**\ In most cases, a workflow won’t work or will result in errors because of modifications to DoControl’s default playbooks. Check that any conditional or array filters in your workflow are configured with the correct values and JSONatas. * **Asset or permission could not be found**\ Sometimes when you try to remediate a permission, the asset was already moved or the permissions were changed. This results in **Warning** status errors that you can see in the workflow execution. * **No permission to perform this action**\ Your integration does not have the necessary permissions to perform remediation. Make sure you have **Write** permissions, then re-integrate your Google account or contact Customer Success for further assistance. * **General errors**\ Please reach out to Customer Success with any questions: \ --- # 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.docontrol.io/docontrol-user-guide/workflows/bulk-remediation/apply-a-bulk-action/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.