Why a scheduled report could not read a site Coming soon
Partial runs, Not read rows and failed runs
Coming soon. This tool is built and shows on its menu, but it does not open in a released build yet. This page describes it as it will ship.
One site or list that cannot be read never stops a scheduled report. The run carries on, the part it could not read is listed as Not read with the reason, and the run is marked Partial rather than Complete. A report with no rows and anything not read is Partial too: an empty result is only reported when everything was actually read.
Reads only. Nothing in SharePoint is changed.
What does it tell you?
- Partial: the workbook is complete except for the parts listed as Not read. The email's first line says how many.
- Not read: usually the reports app's identity was refused (a site with its own restricted access, or a site deleted during the run), or the service was busy for longer than the run could wait.
- Failed: the run could not start or could not finish at all, for example a permission was removed from the reports app's identity. The run says which permission, and setup's Set up / verify puts it back.
- Licence refused: ShareMaster's licence check said no for this tenant. Nothing was read.
- Complete, not all sent: the report ran, but at least one recipient's email was not accepted. Use Resend on that run; the workbook is kept for exactly this.
How it runs
- Find the run. Reports › Scheduled reports, select the schedule, and read its runs. The headline says what was not read.
- Check the site. A site with unique permissions may need the reports identity added, or may be one you meant to leave out.
- Run again. Run now on the schedule runs it again straight away; the next scheduled run happens anyway.
Read next
- Scheduled reports: Scheduling, runs and Resend.
- Setting up scheduled reports: Set up / verify repairs missing permissions.