| Dates are out of range |
If no data is available for the selected time period the report will fail. Ensure the values are actually being stored in the database. If not, verify that the logger is correctly set up. See Loggers for more information. |
| The report is empty |
If no data appears in the report the macro command is most likely failing. This only happens when a custom template is used. Review the macro command configuration in Creating templates |
| Report is not being sent |
The SMTP server may not be configured correctly. Send a test email from the Reports - Schedule view to check. If that works, verify that the email addresses are entered correctly. See Email notifications in the Alarms module for SMTP configuration. |
| Create Report does nothing |
A report cannot be created until at least one signal is selected in the LoggerList. Select a signal and try again. Alarm Reports are exempt, since they include all signals automatically. |
| Values are off by a factor of a thousand |
Check the Unit and Prefix pickers on the report controller. Each selected signal is scaled from its own native prefix to the chosen display unit, so a signal logged in Wh and one logged in kWh in the same report are both converted before reaching the template. See Units and prefixes. |
| Scheduled reports never run |
Confirm that the five-minute schedule in Schedules.kdat calls scReportScheduler.control_trigger(). A call naming any other script object is skipped silently, with no error. |