Forum Discussion
How can I know the timeout settings or retry settings allowed for semantic model on my server?
- 11 months ago
Hi mlane ,
Yes, that document link is correct for rsreportserver.config.
DatabaseQueryTimeout - applies only to the ReportServer DB itself, not your dataset queries.
ProcessTimeout - controls worker process lifetime, not dataset queries.
ScheduledRefreshTimeoutMinutes - the key setting for dataset refresh duration (default 120 minutes).
Retries (4) - hardcoded in PBIRS/SSRS for dataset refresh, not configurable anywhere. The only configurable retry is for subscription delivery (default 3).
In short, you can adjust timeout values (via SSMS or rsreportserver.config), but retry attempts for refresh are fixed and cannot be changed.
Thank you.
Hi mlane
In Power BI Report Server (PBIRS), the timeout and retry attempt settings for data sources aren’t visible directly in the Power BI Service interface or refresh history; instead, they are defined in the data source connection configuration or sometimes controlled by the underlying data provider (e.g., SQL, ODBC, or Oracle driver). For reports deployed to PBIRS, you can check these settings by opening Report Server Configuration Manager or by editing the data source (.rsds) file or the shared dataset definition within the Report Manager web portal. If your data source uses a connection string, parameters like Connect Timeout or Command Timeout can be included there — for example, Command Timeout=600 sets a 10-minute timeout. However, the retry behavior is not configured within PBIRS directly; it’s typically managed by the Power BI Gateway (for cloud) or by the data provider driver itself. For imported Power BI reports, the retry count you see in the refresh history (usually four attempts) is part of Power BI’s built-in retry policy and cannot currently be changed. To confirm or adjust your timeout values, you’ll need to open the report in Power BI Desktop for Report Server, navigate to Data Source Settings → Edit Permissions → Advanced options, and check or modify the command timeout value before redeploying the report to the server.