Issues with Report Refresh – Semantic Model Stuck

[123abc]

Dear Fabric Community,

I am using a Pro license of Power BI and facing an issue where two of my reports are not refreshing. They continue to attempt refreshing the semantic model without success. No error messages are displayed. Interestingly, the reports refresh successfully in Power BI Desktop, but the issue occurs only on the Power BI Service. For the past five days, I have been manually refreshing the reports in Desktop and publishing them to the service daily, but the problem persists.

I have already tried the following steps:

1. Deleted the semantic model and republished it.
2. Created a new workspace and published the reports there.
3. Changed the PBIX file names and republished in both the old and new workspaces.

Despite these attempts, the issue continues. I would greatly appreciate any guidance or suggestions on how to resolve this problem.

Best regards,
Ali Abbas Rajput

My all Connections are also live ... there are no issue in there.

Red highlighted report's semantic models are stuck:

[Wikkleyn_81]

@123abc Have you checked with the Oracle DBA if that query runs on teh database and why it doesn't finish? 

[123abc]

No, Let my check.... but report is properly refreshed on desktop in 2 min 30 sec  but not on BI service...🥺 

[v-sshirivolu]

Hi @123abc ,

It is possible that the refresh is failing due to a scheduled refresh timeout in the Power BI Service, particularly if the dataset refresh is taking longer than the allowed processing window or encountering resource constraints during execution.

Please try:
Reducing the model complexity. Simplifying the model, especially if it involves computationally expensive calculated tables and columns, can help to lower the refresh burden and avoid memory bottlenecks during refresh. If possible, move calculated tables and columns to the data source or ETL processes.

Use incremental refresh for large semantic models. By automatically partitioning large tables, incremental refresh can help to reduce the amount of data that needs to be refreshed. By refreshing only the most recent import partitions, you can significantly reduce the refresh duration, thus making room for more refreshes in a given timespan.

[tayloramy]

Hi @123abc, 

Can you show a screenshot of the refresh history of these models? Hover over them, click the 3 dots beside the name, and click refresh history. 
 

[123abc]

First of all Thank You So mcuh for your quick and prompt response. Thank You Agiain:

Following Error is now showing:

Refresh History is as below:

The detail is as per below:

Further detail is as per below:

[GilbertQ]

Hi @123abc 

With the error that you are showing, it could well be that the data source that you are trying to query could have an issue. What I would recommend doing is going on to your Power BI gateway and making sure that you can connect from the gateway to your data source as well as the gateway can connect to the Power BI service.

[123abc]

My gateways is proper connected as per below connectins detail: