Forum Discussion
Scheduled refresh blocked by “Data source for Query1” (no such query in model) — Power BI Pro
Hi team,
I can’t enable scheduled refresh for a dataset. Manual Refresh in Desktop and publishing to the Service both work, but in the Service I get:
“You can't schedule refresh for this semantic model because the following data sources currently don't support refresh: Data source for Query1.”
There is no query named “Query1” in my model.
Data sources (high level)
Microsoft Planner via Graph/OData/Web (read-only)
SharePoint
What I tried
Re-published PBIX and recreated the dataset
Cleared and re-set data source credentials
Verified Desktop refresh succeeds
Checked for dynamic data source paths / query folding issues
Searched the model for any hidden/renamed “Query1”
Ask
Is Planner/Graph access supported for scheduled refresh in this setup?
- Is there any workaround for it?
Happy to share more details if needed, my goal is to schedule automatic refresh of the dataset and ensure the related dashboard tiles update accordingly
Thank you,
Hi FaresB
The issue you’re encountering happens because some data sources in Power BI do not support scheduled refresh in the Service, even if they refresh fine in Desktop. In your case, the dataset includes Microsoft Planner data accessed via Graph/OData/Web connectors, which are considered read-only API sources. These connectors often do not support scheduled refresh, or they require specific authentication methods that aren’t compatible with the Service refresh engine. The reference to “Query1” is a generic placeholder Power BI uses when it detects an unsupported data source in the model, so it doesn’t necessarily correspond to a query you’ve named. While Desktop refresh works because it runs under your user context with interactive credentials, the Service cannot execute the same calls automatically if the API or connector doesn’t support refresh. Workarounds include using a gateway with a custom connector or Power Automate to pull Planner data into a supported source like SharePoint or Azure SQL, and then connecting your model to that intermediate dataset, allowing scheduled refresh to function. Essentially, for Planner/Graph data, you cannot rely on direct scheduled refresh in Power BI Service; you need to stage the data in a refreshable source first.
8 Replies
- arvindsingh802
Community Champion
v-menakakotaCommunity Support
Hi FaresB ,
Thanks for reaching out to the Microsoft fabric community forum.
I would also take a moment to thank arvindsingh802 , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you.
Best Regards,
Community Support TeamHi Arvindsingh802,
Thank you for sharing this, it makes sense. I can now see the graph URL in the data source settings, but my table is still showing up blank. Could you please take a look at the code I have? Maybe I’m missing something. I’ll gladly accept it as a solution if it works.
Thanks again,
Fares- v-menakakota
Hi FaresB ,
Thank you for the update, If your table is showing up blank, it would really help if you could share the code/query you’re using (make sure to remove or mask any sensitive information such as tenant IDs, tokens, or personal data).
Once we can see the actual query, it’ll be easier to check if there’s anything missing in the steps, such as authentication, headers, or how the data is being expanded.
Best Regards,
Community Support Team.
- Poojara_D12
Super User
Hi FaresB
The issue you’re encountering happens because some data sources in Power BI do not support scheduled refresh in the Service, even if they refresh fine in Desktop. In your case, the dataset includes Microsoft Planner data accessed via Graph/OData/Web connectors, which are considered read-only API sources. These connectors often do not support scheduled refresh, or they require specific authentication methods that aren’t compatible with the Service refresh engine. The reference to “Query1” is a generic placeholder Power BI uses when it detects an unsupported data source in the model, so it doesn’t necessarily correspond to a query you’ve named. While Desktop refresh works because it runs under your user context with interactive credentials, the Service cannot execute the same calls automatically if the API or connector doesn’t support refresh. Workarounds include using a gateway with a custom connector or Power Automate to pull Planner data into a supported source like SharePoint or Azure SQL, and then connecting your model to that intermediate dataset, allowing scheduled refresh to function. Essentially, for Planner/Graph data, you cannot rely on direct scheduled refresh in Power BI Service; you need to stage the data in a refreshable source first.
- v-menakakota
Hi FaresB
Thanks for reaching out to the Microsoft fabric community forum.
I would also take a moment to thank Poojara_D12 , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you.
Best Regards,
Community Support Team Hi Poojara_D12
Thank you—this worked perfectly! Really appreciate your help.
