Refresh failure in Power Bi service/Desktop

Hi priyankakande ,

Thank you for reaching out to Microsoft Fabric Community Forum, Below are the few debug steps which can resolve your issue.

• The 17,999-second timeout indicates that the refresh is taking too long at the data source/query level Since the refresh fails in both Power BI Desktop and Power BI Service, first investigate the source query performance and Power Query transformations.
• Check Query Folding and ensure that the date filter is pushed back to the source system.
• Apply the date filter as early as possible in Power Query, before expensive transformations.
• Test the refresh with a small date range, such as one month, and gradually increase it to identify whether the issue is related to data volume.
• Run the source query directly against the database and check how long it takes to complete.
• Optimize the source query by Removing unnecessary joins and columns, Adding appropriate indexes to filter/join columns where applicable, Moving complex transformations to the source database where possible.
• Reduce the Power BI model size by removing unused columns/tables and unnecessary high-cardinality fields.
• For Incremental Refresh, verify that RangeStart and RangeEnd are correctly configured and that query folding is maintained.
• Keep in mind that the initial refresh after publishing an Incremental Refresh model may still take significant time because historical data must be loaded according to the policy.
• If using an On-premises Data Gateway, verify gateway health, version, CPU/memory availability, and network connectivity.
• After optimizing the source and confirming query folding, test with a small data range, then configure Incremental Refresh and perform a fresh Service refresh.

Thanks,

Chaithanya.