Cannot configure scheduled refresh for my semantic model

Hi KTazmi 

The error message “You can't schedule refresh for this semantic model because the following data sources currently don't support refresh: Data source for Query1” typically occurs when Power BI’s service engine detects unsupported or ambiguous constructs in your Power Query (M) code. Even though your script doesn't explicitly contain a query named "Query1", this label is sometimes assigned by Power BI internally to a step or an unnamed query, especially if something went wrong during publishing or the source wasn't recognized properly. In your case, the usage of Web.Contents with the RelativePath and Query parameters appears correct—and these parameters are indeed required for Power BI to classify the source as refreshable in the service. However, there are a few common pitfalls to check:

First, ensure the URL base domain is constant and literal (not dynamically constructed), as dynamic base URLs can prevent Power BI from recognizing it as a refreshable endpoint. Also, verify that no part of the Web.Contents call uses variables outside the expected syntax (e.g., dynamic API key injection via parameters rather than through the UI-managed credentials). If any values like apiKey are being passed dynamically via M expressions instead of using the “API key” authentication method in the dataset settings, it could flag the connector as unsupported. Additionally, the List.Generate construct sometimes leads to issues if not structured carefully, especially if the stopping condition is dependent on external data or if it triggers recursive web calls.

To resolve it, you can try simplifying the script temporarily to test a basic single-page API call using Web.Contents with RelativePath and Query, and confirm it works with scheduled refresh. If that succeeds, reintroduce paging incrementally. Also, try renaming or checking all query steps in Power BI Desktop to make sure none have retained a default name like "Query1" from earlier development phases. Finally, republish the dataset after a full metadata refresh. If issues persist, capturing a trace log via the diagnostics tool and cross-verifying with Power BI service logs may reveal exactly where it fails.