Forum Discussion
Solved
Scheduled Refresh Disabled Due to Missing Credentials – Unable to Identify Source
Hi all, first time posting here. Hoping someone can help. I'm experiencing an issue with a Power BI semantic model where refresh history shows: "Scheduled refresh has been disabled because at ...
Hi dksmith this usually looks like the model is stuck with a hidden or stale credential reference that you cannot see in the Service.
Because the refresh fails instantly, it normally means the issue happens before execution even starts, during credential validation.What can work in this case is to assume there is a “ghost” source still registered. This often comes from old parameters, disabled queries that are still referenced, or functions using Web.Contents.My suggestion is to start by forcing a full reset of credentials in the Service. Go to the semantic model settings and re-enter credentials for every listed source, even if they already show as valid. This can clear inconsistent states.Another common cause is dynamic sources. Things like GitHub files, APIs, or export URLs can create multiple logical sources in the Service, even if they look like a single source in Desktop. That can trigger this error.It is also worth checking your Power Query logic for hidden references, especially parameters, custom functions, or queries that are not loaded but still used somewhere in the dependency chain.If nothing works, what usually helps is republishing the model as a new dataset and setting up credentials again from scratch. This tends to remove any leftover references in the backend.In practice, the issue is not always about identifying one broken source, but about forcing the Service to revalidate everything cleanly.If you want, you can share part of your M code and I can help check for patterns that typically cause this.
Zanqueta
Super User
Super UserHi dksmith this usually looks like the model is stuck with a hidden or stale credential reference that you cannot see in the Service.
Because the refresh fails instantly, it normally means the issue happens before execution even starts, during credential validation.
What can work in this case is to assume there is a “ghost” source still registered. This often comes from old parameters, disabled queries that are still referenced, or functions using Web.Contents.
My suggestion is to start by forcing a full reset of credentials in the Service. Go to the semantic model settings and re-enter credentials for every listed source, even if they already show as valid. This can clear inconsistent states.
Another common cause is dynamic sources. Things like GitHub files, APIs, or export URLs can create multiple logical sources in the Service, even if they look like a single source in Desktop. That can trigger this error.
It is also worth checking your Power Query logic for hidden references, especially parameters, custom functions, or queries that are not loaded but still used somewhere in the dependency chain.
If nothing works, what usually helps is republishing the model as a new dataset and setting up credentials again from scratch. This tends to remove any leftover references in the backend.
In practice, the issue is not always about identifying one broken source, but about forcing the Service to revalidate everything cleanly.
If you want, you can share part of your M code and I can help check for patterns that typically cause this.