Increasing session timeout for Paginated Reports in Microsoft Fabric

Paginated reports have the potential to do some serious damage to the CUs on your capacities.  Avoid  them whereever possible.

There are capacity settings where you can control the timeout value for Power BI workloads

But be careful - the higher you set that the more your users will hammer the CUs.

1) Optimize the report

Start by looking at what the report is actually returning. If you’re pulling a large, detailed dataset or doing heavy grouping and expressions inside Report Builder, render times will increase quickly. In most cases I’ve seen, long-running paginated reports are simply doing too much work at query time.

2) Use parameters to limit scope

Avoid loading everything by default. Introduce parameters (date range, region, etc.) and make them required. This forces the report to run on a smaller slice of data and usually brings execution time down to a reasonable level.

3) Pre-stage data in Fabric

Since you’re already using Fabric, push the heavy lifting to the SQL endpoint, Warehouse, or Lakehouse. Pre-aggregate or shape the data there, and let the paginated report just read a clean, ready dataset. This is often the biggest improvement you can make.