Scan error

Also known as: scan errors, scan failure

A scan error means Rencore Governance could not read part of your tenant during a scan job. Some objects may then be missing from the inventory or out of date.

Most scan errors come from missing permissions or from a known limit of a Microsoft API. Each scan error guide quotes the exact message, explains the cause and gives the fix.

A scan error does not stop the whole scan. It affects the objects that could not be read, so reports, policies and automations on those objects can show old data until the error is fixed.

For example, Microsoft Graph cannot return a SharePoint site collection with more than 12 subsites. The scan of that site collection stops with the message “The request is unprocessable because it uses too many resources” until you move subsites out.

You find scan errors in the scan job history of the Environment: click Inventory on the Nav Panel, then go to Inventory Options > All scans. The scan error guides cover SharePoint, Teams and Power Platform messages.