Forum Discussion
Helper IISemantic model refresh failed with adotimeout
Hi Ynr225,
As you are experiencing this issue frequently, please submit a support ticket with Microsoft.So that one of the engineers can assist you further, ensuring a thorough investigation and a timely resolution of the Gateway Timeout Error.
Below is the link to raise the support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Thank you.
Helper IIThanks for responding Deku, here the thing is we are getting the above error if user uses import mode where as direct query mode connected report is refreshing in both desktop and service. Don't know why it is happening for import mode.
- Deku
Super User
Other similar posts suggest increaseing the timeout period in the connector settings
- Ynr225
Hello Deku ,
Even I tried the above method in Power BI desktop but no use, still receiving the same error in service.
v-saisrao-msftCommunity Support
Hi Ynr225,
Thank you for reaching out to the Microsoft Fabric community forum. Also, thanks @Deku for your valuable insights.Since you have already increased the timeout in Power BI Desktop but are still encountering the issue in Power BI Service, here are a few options you can consider:
- Limit the dataset size by applying filters in Power Query. Consider splitting the dataset into smaller chunks. If possible, switch to Direct Query mode instead of Import Mode.
- Rather than importing all data at once, use Incremental Refresh to load only new data.
If this information is helpful, please “Accept it as a solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.
