Forum Discussion
Salesforce Object Timeout
Hi Anonymous ,
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.
Hi Andrew,
The "this just started happening" angle is the key clue here. A few likely causes when a previously-working Salesforce Object dataflow starts timing out at 10 minutes:
- Data volume growth - 2M rows + 106 columns is a lot to pull every refresh. Modest org growth (new records, custom fields added) can push you over the 10-min Salesforce REST API ceiling.
- Wider object schema - if 106 columns has grown from 80-90, the auto-generated SELECT is now larger, and the response payload heavier.
- N+1 expansions - if CreateNavigationProperties=true is enabled (it usually is by default), and any of those 106 columns reference relationships, Power Query may be making extra calls per row during expansion.
The fundamental fix is to reduce what you're pulling per refresh. Since you're already removing columns downstream in Power Query, you can move that pruning to the source via the Salesforce.Data Advanced Option → Select Query with custom SOQL listing only the columns you actually use - shorter response, faster pull, no timeout.
If hand-writing SOQL isn't ideal, Power BI Connector for Salesforce on AppExchange handles this through a UI inside Salesforce:
Why it might fit:
- Field selection and filter conditions configured on the Salesforce side - only what you need leaves the org, no timeout on large tables
- No 2,000-row limit on reports
- Supports custom fields, custom objects, and joined reports
- 30-day free trial
- Setup docs: https://metricasoftware.com/docs/salesforce/
- Responsive support if you get stuck: https://metricasoftware.com/docs/salesforce/contact-support/
Happy to set up a quick demo on your 2M-row table specifically. Just reach out via the support link.
Cheers,
Metrica Team.