Scheduled report ends in error

[JeanClaudeS]

How can I be alerted when a scheduled report ends in error or does not run at all?

[Nayan ArchX]

It may be because ServiceNow has started deprecating classic Core UI reports (legacy reporting engine) in favour of Platform Analytics and Data Visualizations

[Ankur Bawiskar]

@Nayan ArchX 

I couldn't find this table in Yokohama instance either.

I don't think ServiceNow removes tables if something is deprecated in this case legacy reporting.

[Nayan ArchX]

Note: Some tables are highly restricted in access by ServiceNow due to the Performance Optimization: ServiceNow advises against reporting on large system tables, as doing so can slow down or crash the instance.

[Ankur Bawiskar]

@JeanClaudeS 

you can check system logs to see if any error thrown

You can also monitor this table (sys_email) and see if any attachment came for that scheduled report

-> just after your scheduled report runs example Daily 10AM, create another scheduled job at 10.05AM and see if there is a record in sys_email with Target=SysId of Scheduled Report and Subject = Your Scheduled Report Subject

-> also check in sys_attachment if file is present for that email record i.e. Table sysId  = Email record sysId

-> if not then it means scheduled report didn't run

-> you can send an email using event to some Team notifying about this

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Ankur Bawiskar]

@JeanClaudeS 

I believe the approach I shared should work for you, please discuss this approach.

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏