Retry attempts for failures while executing the refresh exceeded the retry limit set on the request.

[Anonymous]

Hi Team,

I am facing an issue with my model refresh 

Error Message : 

"Retry attempts for failures while executing the refresh exceeded the retry limit set on the request."

We are triggering our dataset model through XMLA endpoint i.e., refreshing only specific partitions during schedule time. It was failed multiple times bcoz of above error message. Then after , I refreshed the model manually "On demand" and got an correct error message saying that one of the column was not present in the rowset. After fixing that my model executed successfully via "On demand"/XMLA endpoint .

But now , my question is why during XMLA endpoint execution the error message was not provided properly.

[Anonymous]

@Adamboer  - Thank you so much for the detailed explaination.

We already know that for XMLA endpoint the error message was detailed . But seeking for any other solution to fix it.

[Adamboer]

Based on the error message you received, it seems that the model refresh attempts exceeded the retry limit set on the request. This could have been due to an issue with the data source or a problem with the partition refresh configuration.

It's possible that the error message you received during the XMLA endpoint execution was not provided properly because of the way that the refresh process was set up. When refreshing specific partitions using XMLA, the error message may not be as detailed or specific as when refreshing the entire model manually "On demand". This could be because the refresh process using XMLA is more automated and may not provide the same level of detailed feedback as a manual refresh.

Another possible reason for the lack of detailed error message during the XMLA endpoint execution could be related to the version of Power BI that you are using. It's possible that some versions of Power BI may provide more detailed error messages than others during the refresh process.

In any case, it's important to make sure that your data source and partition refresh configuration are set up correctly, and to monitor the refresh process to catch any errors that may occur. You can also try to replicate the issue and see if you can reproduce the same error message using a test data source and partition configuration.

I hope this helps! Let me know if you have any other questions or if there's anything else I can assist you with.