Dynamic Subscription failing "PaginatedReportUnknownError"

Hey FrankZandbergen , 

This kind of error can be confusing, especially since your report is not a paginated report, yet the error message says “PaginatedReportUnknownError.”

Here’s what’s likely happening and what to check:

• Sometimes Power BI’s subscription system uses shared infrastructure for both paginated and regular reports behind the scenes. So even if your report isn’t paginated, errors can still show up with the “PaginatedReport” label basically a misleading or generic error message.
• This error often means there’s a problem generating or delivering the subscription email, but the root cause can vary:
  • It could be due to a temporary service glitch on Power BI’s side.
  • Or your subscription’s dynamic parameters or dataset query might be running into issues (like timing out or permission changes).
  • Another possibility is a change in workspace or report permissions that breaks the subscription access.
  • Sometimes, if the subscription’s recipient list is dynamic and references a user or group that no longer exists or lacks access, it can cause failures.
• Since this was working fine for a long time, think about what has changed recently:
  • Have there been any changes in workspace roles, report permissions, or dataset credentials?
  • Has the Power BI service or tenant received any updates or policy changes (like email restrictions)?
  • Are there any data refresh failures that might cause the report to be temporarily inaccessible when the subscription tries to run?

What you can try right now:

1. Check the refresh history of the dataset feeding the report. If refresh fails, subscriptions often fail too.
2. Validate the dynamic parameters or recipient list in the subscription  make sure all emails or groups are still valid.
3. Recreate the subscription from scratch. Sometimes just deleting and recreating fixes hidden glitches.
4. Check Power BI Service health on Microsoft’s status page for any ongoing issues.
5. If the problem persists, open a support ticket with Microsoft, providing the subscription ID and timestamps. This error is known to sometimes require backend fixes.

If this explanation helped, please mark it as the solution so others can find it easily.

If it helped, a quick Kudos is always appreciated it highlights useful answers for the community.

Thanks for being part of the discussion !!!