Frequent Failures in Scheduled Report

Question

We have been scheduling and receiving various types of reports, including revenue reports, through the following URL:

https://partner.microsoft.com/en-us/dashboard/insights/analytics/downloadshub

However, since February 27, report generation has been inconsistent, with frequent failures occurring across all associated accounts.

Could you please help us identify the issue and suggest a solution?

Thank you for your support.

Answer 1

Downloads hub itself is working by design, but there are product-side limits and behaviors that can explain inconsistent or failed report generation. The context does not expose any tenant‑specific diagnostics, so only general causes and remediation steps supported by documentation can be provided.

Key points from the product behavior and limits:

1. Scheduling limits per user and program
   • Each program in Downloads hub has a hard cap of 40 scheduled reports per user.
   • If this limit is exceeded, new schedules cannot be created and existing ones may not execute as expected.
   • Verify under Reports scheduled that the total count per program and user is within this limit.
2. Time‑range restrictions for scheduled reports
   • When scheduling, the allowed time range depends on frequency:
     • Daily: last 30 days
     • Weekly: last 30 days
     • Monthly: last two years
     • Yearly: last year
   • If a scheduled report uses a time range outside these limits, it will not be accepted or may fail. Ensure each schedule complies with these ranges.
3. Execution limits for recurring schedules
   • Each schedule has a maximum number of executions:
     • Daily: up to 180 runs (about six months)
     • Weekly: up to 52 runs (one year)
     • Monthly: up to 24 runs (two years)
     • Yearly: up to 5 runs (five years)
   • After these execution limits are reached, the schedule stops running. Check whether long‑running schedules have simply reached their maximum execution count and recreate them if needed.
4. Report generation concurrency and completion window
   • Downloads hub allows five reports in download to complete within 60 minutes.
   • If many reports are triggered at once (manually or via multiple schedules), some may queue or fail. Stagger schedules across different times and reduce parallel one‑time runs to stay within this concurrency envelope.
5. Data availability windows
   • For Marketplace revenue data specifically:
     • Subscription‑based transactions have up to 24 hours latency.
     • Usage‑based transactions can have latency up to the 7th of the following month.
   • If the scheduled reports are targeting very recent usage‑based data, some runs may appear incomplete or fail due to data not yet being available. Align schedules (especially monthly usage reports) to run on or after the 7th of the month.
6. Report retention and download behavior
   • Under My reports, only reports generated in the last 90 days remain accessible; older ones disappear from the table.
   • For Marketplace offers, reports are only downloadable for the last 36 months of data. If a schedule requests data older than 36 months, it will not succeed.
7. What to verify in your environment For each of the affected accounts:
   1. Go to Downloads hub → Reports scheduled and:
      • Count scheduled reports per program and user; reduce to ≤40 if higher.
      • Open each failing schedule and confirm the frequency and time range comply with the documented limits.
      • Check whether long‑running schedules have reached their execution caps; if so, recreate them.
   2. Go to My reports and review the Status/Actions column for failed runs:
      • If many reports are in “Running” or “Preparing download” simultaneously, reduce concurrent triggers.
      • Confirm that the requested time range is within the last 36 months.
   3. For revenue reports specifically, adjust schedules so that:
      • Daily/weekly subscription‑focused reports run at least 24 hours after the period ends.
      • Usage‑based monthly reports run on or after the 7th of the following month.

If, after aligning with these limits and behaviors, failures continue across all three accounts, the next step is to open a support request from Partner Center so that Microsoft can review tenant‑specific logs and configuration, as this level of detail is not exposed in public documentation.

---

References:

• Downloads hub – Microsoft Marketplace Offers
• Revenue dashboard in Microsoft Marketplace analytics
• Downloads hub overview
• Get unified Partner Center insights
• Referrals Downloads Hub overview
• Microsoft Marketplace analytics Frequently Asked Questions