Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
Andshepch
Advocate II
Advocate II

Salesforce Object Timeout

Hi all, I have had a dataflow working for over a year that has worked without any problem. It imports tables using the Salesforce Object connector, and then removes columns that I don't need for the reports that are generated. One of the tables is large and has c.2m rows and 106 columns. Other than that there are no further transformations. For some reason, this query will no longer refresh, and I get the following error message "Data Source Error : DataSource.Error: The operation has timed out" - this always happens at around 10m 46 Seconds after the refresh starts. As I said this has only jst started happening, and I seem to be going round in circles with our Salesforce and Power Platform technical support. Does anyone have any idea what is happening? Thanks in advance.

 

(googling the Salesforce API there is mention of a 10 minute timeout, but this never happened before)

 

Andrew

1 ACCEPTED SOLUTION
v-junyant-msft
Community Support
Community Support

Hi @Andshepch ,

I can provide you with some troubleshooting ideas to assist you in troubleshooting.
Please verify if there are any recent changes to the Salesforce environment that may affect API performance. Also ensure that there are no changes in your network environment that could cause connectivity issues.
Then please verify that the Salesforce Object Connector is working properly and that there are no issues with connectivity. Verify that Salesforce API limits have not changed or that you are not reaching them due to increased data volume or refresh frequency.
Power Query Salesforce Objects connector - Power Query | Microsoft Learn
If these are fine, try optimizing the query. You can try reducing the amount of data transferred by filtering out unnecessary columns or rows. You can also try splitting the data into smaller chunks to reduce the load on the server.
If none of the above steps work, you can try increasing the timeout limit for the data source.
Understand and optimize dataflows refresh - Power BI | Microsoft Learn

On the other hand I found a similar post that might be helpful to you.
Solved: Experiencing Time Out error: “The operation has ti... - Microsoft Fabric Community

Best Regards,
Dino Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

2 REPLIES 2
EugeneLebedev
Helper IV
Helper IV

This basically means you hit an API limit with Salesforce Object. This happens sometimes as the volume of your data grows. 

 

I would recommend to use Salesforce Reports connector instead of Salesforce object. It is a lot faster to load . It is really the most convenient way of extracting data into Power BI since all your needed columns are in one table there.

Salesforce Object connector also sometimes takes ages to load the data. I used to wait for hours for a preview of my tables to load in Power Query.

It only allows you to extract 2000 rows though. However, you can work around this limitation using third-party tools. Here is the approach that I would recommend: https://vidi-corp.com/connect-salesforce-reports-to-power-bi/

v-junyant-msft
Community Support
Community Support

Hi @Andshepch ,

I can provide you with some troubleshooting ideas to assist you in troubleshooting.
Please verify if there are any recent changes to the Salesforce environment that may affect API performance. Also ensure that there are no changes in your network environment that could cause connectivity issues.
Then please verify that the Salesforce Object Connector is working properly and that there are no issues with connectivity. Verify that Salesforce API limits have not changed or that you are not reaching them due to increased data volume or refresh frequency.
Power Query Salesforce Objects connector - Power Query | Microsoft Learn
If these are fine, try optimizing the query. You can try reducing the amount of data transferred by filtering out unnecessary columns or rows. You can also try splitting the data into smaller chunks to reduce the load on the server.
If none of the above steps work, you can try increasing the timeout limit for the data source.
Understand and optimize dataflows refresh - Power BI | Microsoft Learn

On the other hand I found a similar post that might be helpful to you.
Solved: Experiencing Time Out error: “The operation has ti... - Microsoft Fabric Community

Best Regards,
Dino Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
July 2024 Power BI Update

Power BI Monthly Update - July 2024

Check out the July 2024 Power BI update to learn about new features.

July Newsletter

Fabric Community Update - July 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors