Troubleshooting
AI summary
Find troubleshooting guidance for your Rencore Governance issue: sign-in consent prompts, automation errors, missing permissions, scan errors, or Rencore Teams App issues.
Common issues and errors when using Rencore Governance, and how to resolve them. Start with the common issues page for sign-in consent prompts, automation templateAutomationAn automation is a workflow Rencore Governance runs on inventory objects when a trigger fires.Read more errors and missing permissions. Scan errorsScan errorA scan error means Rencore Governance could not read part of your tenant during a scan job.Read more explains the messages a scan jobScanA scan is how Rencore Governance reads metadata from a connected tenant into the inventory.Read more can report and how to fix each one; automation errors and Rencore Teams AppRencore Teams AppThe Rencore Teams App (formerly Rencore Nova) brings Rencore Governance into Microsoft Teams for the people who own and use workspaces.Read more issues have their own pages, linked below.
Start with
- Common troubleshooting issues Solutions to common Rencore Governance issues: sign-in consent prompts, automation template errors, and missing permissions.
- Scan errors What each scan error message means, why it happens and how to fix it.
- Troubleshoot automation errors Find out why an automation run failed, using the Automation Batch Page.
- Fix Rencore Teams App connection messages What the Rencore Teams App error messages mean and how to fix them.
All guides in troubleshooting
-
Solutions to common Rencore Governance issues: sign-in consent prompts, automation template errors, and missing…
Scan errors 6 guides
What each scan error message means, why it happens and how to fix it.
-
Power Platform: the user cannot be created in Microsoft Dataverse
Fix a Power Platform scan that fails because the scanning account is not in the right security group.
2 steps
Power Apps
Power AutomateScanning -
Power Platform: user does not have sufficient permissions in Microsoft Dataverse for flow
Fix a Power Automate scan that fails for lack of Dataverse permissions on a flow.
3 steps
Power AutomateScanning -
Power Platform: failed to create a Microsoft Dataverse system row representing user
Fix a Power Platform scan that cannot add the scanning user to Dataverse.
3 steps
Power AppsPower AutomateScanning
Show 3 guides more
-
SharePoint: forbidden, access denied to resource
Fix a SharePoint scan error about a site icon that tenant policies block.
SharePointScanning -
Why a site collection with too many subsites cannot be scanned.
2 steps
SharePointScanning -
A Microsoft Graph bug stops the scan of Teams channel tabs when a tab has no name.
2 steps
TeamsScanning
Frequently asked questions
Where can I find help with sign-in consent prompts in Rencore Governance?
The Common troubleshooting issues guide covers sign-in consent prompts. It also covers automation template errors and missing permissions.
How do I find out why an automation run failed?
Use the Automation Batch Page. The Troubleshoot automation errors guide explains how to find the reason a run failed.
Where can I look up what a scan error message means?
The Scan errors guides explain what each scan error message means, why it happens and how to fix it. They cover Power Platform, SharePoint and Teams scan errors.
What should I do when a Power Platform scan cannot create the user in Microsoft Dataverse?
What should I do when a Power Platform scan cannot create the user in Microsoft Dataverse?Check the security group of the scanning account. This scan error happens because the scanning account is not in the right security group, and a dedicated guide walks through the fix.
Why can a SharePoint site collection with too many subsites not be scanned?
Why can a SharePoint site collection with too many subsites not be scanned?A site collection with too many subsites cannot be scanned. The SharePoint: too many subsites guide explains why this happens and how to deal with it.