> 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/help/troubleshooting/remediation-issues/zoom-remediation-issues.md).

# Zoom remediation issues

## Warning and failure errors

Troubleshoot any displayed warning errors for Zoom remediation actions:

<table><thead><tr><th width="177">Zoom error</th><th width="104.33333333333331">Status</th><th width="218">Action</th><th>Troubleshooting</th></tr></thead><tbody><tr><td>File format not supported</td><td>Warning</td><td><ul><li>PII scan</li></ul></td><td>Ensure that the file type is supported for PII scanning. See <a href="/docontrol-user-guide/system-management/settings/lexical-lists.md">lexical lists</a>.</td></tr><tr><td>File size not supported</td><td>Warning</td><td><ul><li>PII scan</li></ul></td><td>Maximum file size for running a PII scan is 10 MB.</td></tr><tr><td>Item not found  (asset or collaborator)</td><td>Warning</td><td><ul><li>Change recording visibility</li><li>Delete recording</li><li>PII scan</li></ul></td><td>The file was deleted or could not be found according to the action step settings.</td></tr><tr><td>Not authorized</td><td>Failure</td><td><ul><li>Change recording visibility</li><li>Delete recording</li><li>PII scan</li></ul></td><td>Check integration status, try to re-integrate or contact DoControl support</td></tr><tr><td>Other internal error</td><td>Failure</td><td><ul><li>Change recording visibility</li><li>Delete recording</li><li>PII scan</li></ul></td><td>Contact DoControl Support</td></tr></tbody></table>

## Passcode-protected recordings are not detected

After recording a meeting, I enabled the Zoom setting: "**passcode access to shared cloud recordings is set to enabled"** but the recording is not displayed in DoControl's inventory as passcode-protected.

#### **How to solve this issue**

For DoControl to detect shared recordings as passcode-protected, you must enable the passcode protection security setting across the organization **before** you generate a recording.

If you don't apply this security setting on the organizational level, or you apply the setting **after** the recording was generated, the Zoom API will **not** detect the recording as passcode-protected.

This limitation affects the way Zoom recordings are displayed in DoControl.

* To maintain data integrity, we recommend enabling the Zoom passcode protection setting across your organization.
* Even after you enable this setting, users can still change or remove the passcode.

{% hint style="success" %}

* If your organization is CIS-compliant, you are required to ensure that **passcode access to shared cloud recordings** is set to enabled.
* You can confirm if your organization passes this security check within DoControl's [Misconfiguration](https://app.docontrol.io/misconfigurations?misconfigurations.filters=JTVCJTdCJTIyYXBwJTIyJTNBJTdCJTIyb3BlcmF0b3IlMjIlM0ElMjJJTiUyMiUyQyUyMnZhbHVlJTIyJTNBJTVCJTIyWk9PTSUyMiU1RCU3RCU3RCUyQyU3QiUyMnNlY3VyaXR5Q2hlY2slMjIlM0ElN0IlMjJzaW5nbGUlMjIlM0ElN0IlMjJvcGVyYXRvciUyMiUzQSUyMkNPTlRBSU5TJTIyJTJDJTIydmFsdWUlMjIlM0ElMjJyZXF1aXJlJTIwcGFzc2NvZGUlMjIlN0QlN0QlN0QlNUQ%3D) module.
  {% endhint %}


---

# 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/help/troubleshooting/remediation-issues/zoom-remediation-issues.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.