Scheduled refresh and Manual refresh Error

Hi Saldy123​ 

Please see if these points help you in diagnosing this issue.

1. Check which query is failing. In Power BI Desktop, go to Transform data and test the Business Central queries individually using Refresh Preview. If one looks problematic, try applying a temporary date filter and removing columns you don't need to see whether reducing the data volume makes a difference.

2. Check the Business Central side. Since the refresh is failing repeatedly after around 1.5–2 minutes, check the server logs or available telemetry around those times for terminated requests, timeouts or resource issues. If it's an on-premises setup, also check CPU and memory usage.

3. Compare Desktop and Service. Try a full refresh in Desktop and compare it with the Service refresh history. If Desktop works but the Service fails, I'd look at the gateway and service connectivity. If both fail, I'd focus first on the query and source endpoint.

4. Look at the OData endpoint. If you're using an OData web service, check whether a suitable Business Central API is available. Microsoft recommends APIs over OData web services for supported Business Central Online integrations because of their performance and stability benefits. If the query involves a large volume of data, optimizing the query or staging the data before loading it into the semantic model may also help.

Microsoft also documents this error in the context of transient Dataflow refresh failures, so a retry is worth trying. https://learn.microsoft.com/en-us/dynamics365/business-central/admin-powerbi-setup#exposedata

If this post helps, please accept this as a solution. Appreciate your kudos.

Regards,

Pallavi

Hi Saldy123,

I think the key point is that this error comes from the connection to Business Central being dropped, and it usually means the request was too heavy or was cut off on the Business Central side. It is not a problem in the report itself, which is why it can start after a year of working fine.

The message says the remote host closed an existing connection after about 1 to 2 minutes. Business Central online applies limits to web service requests, such as request throttling and timeouts, and a table that has grown can cross those limits over time. The limits are listed in the Business Central operational limits

Since it started suddenly 3 days ago, it is also worth checking whether the Business Central environment was updated or had a service incident around that date. If other people are seeing the same error with the same connector, that points to the source and not to your refresh settings. The general refresh troubleshooting steps are in the Power BI refresh troubleshooting guide

So I would narrow it down in this order

1. Refresh the table in Power BI Desktop -> same error? -> source or query problem
2. Fewer rows or columns, or a date filter -> works? -> request size problem
3. Service health of the Business Central environment -> incident or update around the failure date?
4. Failing table only -> split it, or use incremental refresh
Connection closed after 1-2 min -> request cut off -> not a report bug

If the same table also fails in Desktop, the Power Query step that loads it is the first place to reduce the load, for example by selecting only the columns you need and filtering the rows as early as possible. If Desktop works but the service fails, check the gateway or the credentials for the connector.

So I would first test the failing table alone with fewer rows, and compare the failure date with any Business Central update or incident. Please share what you find and mark a reply as the solution if it helps.

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.

Hi Saldy123​ ,

Could you review the suggestion provided above and let us know if you have any additional questions, we are happy to address. 

Thanks!!

Hi Saldy123​ ,

Could you check the suggestion provided above and let us know if you have any additional queries?

Thanks!!