Cannot configure scheduled refresh for my semantic model

[KTazmi]

We get the error: You can't schedule refresh for this semantic model because the following data sources currently don't support refresh: Data source for Query1. Firstly, there's no Query1 in the semantic model. Secondly, we make use of paginated API calls, however the calls make use of the WebContents in combination with RelativePath, so this shouldn't cause an issue.

Anyone here had the same issue? I can't seem to get a working fix in Power Query.

[v-sshirivolu]

Hi @KTazmi ,

Thanks for reaching out to the Microsoft fabric community forum.

The issue occurs because Power BI requires the root URL in Web.Contents to be a static literal string. Even though you're using RelativePath correctly, if the domain or root URL is built dynamically, it disables scheduled refresh. Replace any dynamic construction of the base URL with a hardcoded string like "https://your-api-url.com", and keep only dynamic parts in RelativePath and Query.

Use a Static Base URL in Web.Contents

Do not assign apiUrl from parameters or variables; the top-level domain must be a constant string for compatibility with Power BI Service.

Refer Below Doc for your reference :

Web.Contents limitations for scheduled refresh

Configure Web.Contents with RelativePath and Query

This approach is supported in Power BI Service only when the base URL remains fixed.

Refer Below Doc for your reference :

Power BI and REST APIs - pagination pattern

Using Web.Contents with RelativePath

Add the API to Power BI Service Data Source Settings

After publishing your report: Navigate to Power BI Service -Settings - Dataset - Data Source Credentials

Verify that API credentials are properly set up

Select Anonymous or Web API key based on your authentication method.

Refer Below Doc for your reference :

Configure data source credentials in Power BI Service

Gateway Requirement for On-Premises or Private APIs

If your API is not publicly accessible, ensure you use an On-premises data gateway.

Refer Below Doc for your reference :

On-premises data gateway overview

Regads,
Sreeteja
Community Support Team.

[v-sshirivolu]

Hi @KTazmi  ,
May I ask if you have resolved this issue? If so, please mark the helpful reply. This will be helpful for other community members who have similar problems to solve it faster.

[v-sshirivolu]

Hi @KTazmi ,

Just wanted to check if you had the opportunity to review the suggestion provided?

[v-sshirivolu]

Hi @KTazmi  ,

I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.

[Poojara_D12 · Accepted solution]

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.

[cpwebb]

If this works in Desktop and not in the Service, the reason is probably that ApiKeyName authentication isn't supported in the Service - it certainly wasn't supported a few years ago when I last checked with the relevant developer and I don't think the situation has changed since then.