Forum Discussion

Rabin_01's avatar
Rabin_01
New Member
1 month ago
Solved

Power BI Refresh Fails with “Unable to Continue Fetch After Reconnect” from Azure Databricks.

Hi Everyone,
I’m refreshing a report with dataset (~10 million rows) from Azure Databricks. The refresh runs for about an hour and then fails with the following error:

Unable to continue fetch after reconnect. Retry limit exceeded.

 

Error Message:

Data source error: {
"error": {
"code": "DM_GWPipeline_Gateway_MashupDataAccessError",
"pbi.error": {
"code": "DM_GWPipeline_Gateway_MashupDataAccessError",
"parameters": {},
"details": [
{
"code": "DM_ErrorDetailNameCode_UnderlyingErrorMessage",
"detail": {
"type": 1,
"value": "[Microsoft][Hardy] (35) Error from server: Unable to continue fetch after reconnect. Retry limit exceeded."
}
},
{
"code": "DM_ErrorDetailNameCode_UnderlyingHResult",
"detail": {
"type": 1,
"value": "-2147467259"
}
}
],
"exceptionCulprit": 1
}
}
}

Cluster URI: WABI-INDIA-CENTRAL-A-PRIMARY-redirect.analysis.windows.net
Activity ID: 4f41bd35-ef03-48a5-8b07-57c9b554f648
Request ID: 689cf96f-f8d7-c53e-b6d6-f4eb4e4c5d57
Time: 2026-07-30 13:35:27Z

 

Has anyone experienced this issue or found a solution? Any suggestions would be appreciated.

 

Thank you!

Need Help
  • DanieleUgoCopp's avatar
    DanieleUgoCopp
    1 month ago

    Hello,
    Based on the error and the one-hour refresh time, the most likely culprit is an authentication token expiration. If you're using a Service Principal (SPN) or OAuth for authentication, the token often has a 1-hour lifetime, which would cause the fetch to fail right around the time your refresh is failing    . The fix for this is to switch your connection to use a Personal Access Token (PAT) instead. Many users have reported that this resolves the issue because the PAT doesn't have the same hard 1-hour limit.
    Best regards,
    Daniele

3 Replies

  • DanieleUgoCopp's avatar
    DanieleUgoCopp
    Icon for Super User rankSuper User
    1 month ago

    Hello,
    Based on the error and the one-hour refresh time, the most likely culprit is an authentication token expiration. If you're using a Service Principal (SPN) or OAuth for authentication, the token often has a 1-hour lifetime, which would cause the fetch to fail right around the time your refresh is failing    . The fix for this is to switch your connection to use a Personal Access Token (PAT) instead. Many users have reported that this resolves the issue because the PAT doesn't have the same hard 1-hour limit.
    Best regards,
    Daniele

    • Rabin_01's avatar
      Rabin_01
      New Member
      1 month ago

      Hi DanieleUgoCopp , Thank you for your suggestion. I have a question regarding the PAT configuration.

      In Power BI, when I connect to Azure Databricks, I provide the Server Hostname and HTTP Path. The available authentication options are Azure Active Directory (default - which we prefer currently), Personal Access Token, and Databricks Client credentials. We also use an On-premises Data Gateway to refresh the dataset in the Power BI Service.

      I'm not sure where exactly the PAT should be configured. Should I change the authentication method to Access Token in Power BI Desktop when connecting to the Databricks SQL Warehouse, or should it be configured in the Gateway data source in the Power BI Service?

      I tested using a PAT in Power BI Desktop by selecting Personal Access Token during authentication, but I'm still getting the same error after publishing and refreshing the dataset.

      Could you clarify the correct place to configure the PAT, or whether there are any additional gateway settings that also need to be updated?

  • v-sathmakuri's avatar
    v-sathmakuri
    Icon for Community Support rankCommunity Support
    1 month ago

    Hi Rabin_01 ,

     

    Thank you for reaching out to fabric community.

     

    If you switch to a Personal Access Token (PAT) in Power BI Desktop, make sure you also update the gateway data source credentials in the Power BI Service to use the same authentication method. Otherwise, the Service refresh may continue using the previous Azure AD credentials.

     

    Since you have already tested PAT and are still seeing the "Unable to continue fetch after reconnect. Retry limit exceeded." error, it's likely that authentication isn't the root cause. This error is more commonly associated with the Databricks session being interrupted or timing out during a long-running query.

     

    I would recommend checking the following:

     

    • Whether the refresh consistently fails after about the same duration (around 1 hour), as this may indicate a SQL Warehouse or network timeout.
    • The Databricks SQL Warehouse/cluster logs around the time of the failure to see if the session was terminated or the warehouse restarted.
    • The On-premises Data Gateway logs for any network disconnects, retries or gateway-related errors during the refresh.

     

    Thanks!!