Datto EDR Reports: Delayed or Failing to Generate

Issue ID: EDR-03
Applies to: Datto EDR
Environment: Datto EDR console/portal-side (not OS-specific)
KB type: Troubleshooting


Issue

This article applies when a scheduled or on-demand Datto EDR report does not generate within the expected time or fails to generate at all.


Symptoms

  • Report status remains “Pending” or “In Progress” well beyond the normal generation time.
  • Scheduled report does not arrive or generate as expected.
  • Manually triggered report generation fails with no output.
  • Error message displayed, such as “Failed: Unable to complete report.”

Causes

  • High data volume or large date range selected for the report.
  • Backend processing delays, especially during peak times (e.g., first day of the month or week).
  • Backend service issues or outages.
  • Data retention limits impacting report availability.

Troubleshooting Steps

Follow these steps to resolve delayed or failed report generation:

  1. Confirm expected generation time
    • Most reports should generate in under 5 minutes. Generation times longer than 15 minutes are considered unexpected and may indicate an issue.
  2. Check report status and errors
    • Locate the report task in the Task List within the Datto EDR console.
    • Review the status and look for error messages such as “Failed: Unable to complete report.”
      • If this error appears, recent engineering fixes may have resolved the issue. If the error persists, proceed to escalation.
  3. Record report details
    • Note the report type, parameters (date range, scope), and the time it was requested.
  4. Test with a smaller scope
    • Attempt to generate the same report with a reduced date range or smaller data set.
    • If the smaller report succeeds but the larger one fails, this suggests a data volume or timeout issue.
  5. Consider peak time delays
    • If the report was scheduled during a peak period (e.g., first day of the month/week), delays or failures may occur.
    • Reschedule the report for an off-peak time or generate it manually (ad-hoc).
  6. Check for data retention limits
  7. If unresolved, contact Kaseya Support
    • If the report remains stuck or fails after following the above steps, contact Kaseya Support.
    • Provide the report type, parameters, timestamps, and any error messages.

Notes

  • A smaller-scope report succeeding while a larger one fails is a strong indicator of a data volume or timeout issue.

Related Articles

 

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section