Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Learn more
So I can tell from the refresh history that I have about 5 datasources that were set to have timeout and retry attempts. It looks like it retries about 4 times. How can I tell the number of retry attempts a datasource has on my server? Or the current time out value?
I am just not sure where those settings might be.
Solved! Go to Solution.
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.
Hi @mlane ,
May I ask if you have resolved this issue? Please let us know if you have any further issues, we are happy to help.
Thank you.
Hi @mlane ,
I wanted to check if you had the opportunity to review the information provided and resolve the issue..?Please let us know if you need any further assistance.We are happy to help.
Thank you.
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 ,
Thank you for reaching out to Microsoft Fabric Community.
Thank you @tayloramy for the prompt response.
Timeouts - These are set at the data source or dataset level. You can check or adjust them in SSMS (Reporting Services instance) or in the rsreportserver.config file. If not set, the default is usually 120 seconds.
Retries - The 4 retry attempts you see in refresh history are hardcoded by PBIRS/SSRS for transient failures. They are not configurable anywhere.
So,you can view/change timeout in SSMS or config.Retry count cannot be changed - it’s built into the engine.
@tayloramy and @v-venuppu 
   I have a few follow up questions.  .  I suspect strongly that I am connected to a single database node Reporting Server Database (connected to SSRS) for a multi-database SQL Server Network.   I have some admin access to the PowerBI, but nothing to the sql server  However, I will need to confirm this.  For say of discussion the entire SQL Server Network is called CAD and the specific database node I connect to is RDW1CAD
I have additional more critical follow up questions about the Power BI Side.  But to not confuse my team I need seperate the conversation. 
First my questions about the dataset level RDW1CAD.   
Hi @mlane,
Do you have permissions to remote into the server hosting PBIRS?
If so, you can connect to the reporting services in SSMS and see all the settings in there.
If you don't have access you will need to work with your IT team that does have access to be able to get this info.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Thanks for your reply!  I am going to merge the discussion to what venpuu was saying.
I am some permission to pull data from the remote server and I work with the person who has direct access.  I need to know what settings I am looking for in the power bi gateway and its configuration file. 
Hi @mlane, 
Once connected to the report server in SSMS, go to server properties -> advanced: 
under other there is sessionTimeout: 
and then under user-defined are a lot more timeouts like:
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.   
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
Check out the October 2025 Power BI update to learn about new features.
            | User | Count | 
|---|---|
| 5 | |
| 3 | |
| 2 | |
| 1 | |
| 1 | 
| User | Count | 
|---|---|
| 10 | |
| 5 | |
| 5 | |
| 5 | |
| 4 |