Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now

Scheduled Refresh Fails to Re-enable on Data Credential Update

Dataset resides on PowerBI Premium Capacity

 

Scenario 1:

* New dataset with scheduled refresh configured through the dataset settings in the UI

* Weeks later, data source credentials fail due to expired password.

* To remediate, I logged into app.powerbi.com....

* Selected the Dataset settings....

* And updated and saved the new password....

* The issue is that scheduled refresh settings are not automatically re-enabled. 

 

My scheduled refresh settings should not have to be manually restored in this scenario. 

 

----------------------------------------------------------------

 

Scenario 2:

* Dataset configured with scheduled refreshes through the app.powerbi.com UI.

* Datasets start failing with this error: "The last refresh attempt failed because of an internal service error"

* Per the refresh history, it looks like scheduled refreshes are disabled after 4 consecutive unsuccessful refresh attempts.

* Later, I log on and manually refresh, and the refresh succeeds.

* The issue is that schedule refresh settings are not automatically re-enabled.

 

My schedule refresh settings should not have to be manually restored in this scenario. 

Status: New
Comments
v-qiuyu-msft
Community Support

Hi @Anonymous,

 

1. You can submit a idea here: https://ideas.powerbi.com/forums/265200-power-bi-ideas

2. There can be many facts cause the internal service error. It's a general error message "The last refresh attempt failed because of an internal service error". After you turn on the schedule refresh, does the dataset refresh fine now? 

 

Best Regards,
Qiuyun Yu 

Anonymous
Not applicable

Hi @v-qiuyu-msft,

 

To answer your question: yes, when I turn on the scheduled refresh, it works fine.

 

As a workaround, I have leveraged the Power BI RestAPI to perform refeshes via script so I don't have to re-enable through the UI every time this occurs. IMO, this is definitely a defect. 

 

Thanks!