Forum Discussion
Dataflow running late
Hi brunoctesser ,
Thank you for reaching out to the Microsoft Fabric community.
We have verified that everything is set up correctly, but you are still encountering the issue. Before raising a ticket, could you please check the following method. If the issue persists, you may proceed with raising a ticket as mentioned uzuntasgokberk .
Another option to consider, if you need all that data, is to use direct query for dataflows.
Using DirectQuery with dataflows - Power BI | Microsoft Learn.
Aggregations in Power BI can improve query performance over large DirectQuery semantic models. By using aggregations, you cache data at the aggregated level in-memory.
User-defined aggregations - Power BI | Microsoft Learn
Note: That this functionality is available only with premium or premium per user, as it requires enabling the 'Enhanced compute engine settings' for the Dataflow.
We have mentioned the link below, which is like your issue and provides better clarity. Please check it once.
Solved: Power BI dataflow very slow - Microsoft Fabric Community.
If my answer addressed your query, kindly mark it as the Accepted Solution to assist others.
I'd also be grateful for a 'Kudos' if you found my response useful!
Hello uzuntasgokberk , thank you for your response. The timezone is set correctly. In the example it took slightly above one hour, but sometimes it takes 46 or 50 minutes.
Hello brunoctesser ,
So it’s correct that the next refresh always displays the time in your local time zone. The 'Refreshed' timestamp will show once the refresh has actually completed. If the refresh takes 50 minutes, for instance, you might see 01/12/2025 6:50 PM. In your screenshot, the refresh took 62 minutes, which is why it shows 01/12/2025 07:02 PM.
Kind Regards,
Gökberk Uzuntaş
📌 If this post helps, then please consider Accepting it as a solution and giving Kudos — it helps other members find answers faster!
🔗 Stay Connected:
📘 Medium |
📺 YouTube |
💼 LinkedIn |
📷 Instagram |
🐦 X |
👽 Reddit |
🌐 Website |
🎵 TikTok |
uzuntasgokberk , actually the refresh took one and half minute, as you can see in the image below. It was scheduled for 6PM, started at 7:01:02PM, took 1 minute and 28 seconds, and ended at 07:02:30PM.
Hello brunoctesser ,
Interesting. If it's an on-demand refresh, that makes sense since it refreshes whenever you trigger it. But if it's a scheduled refresh, you might consider raising a ticket.
If you have a Pro license you can open a Pro ticket about your issue at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .Kind Regards,
Gökberk Uzuntaş
📌 If this post helps, then please consider Accepting it as a solution and giving Kudos — it helps other members find answers faster!
🔗 Stay Connected:
📘 Medium |
📺 YouTube |
💼 LinkedIn |
📷 Instagram |
🐦 X |
👽 Reddit |
🌐 Website |
🎵 TikTok |Hello brunoctesser ,
By the way, I tested it. It seems yours is set to On-Demand, which means you manually trigger the refresh that can be powerautomate or with your trigger. The timestamp therefore appeared to reflect the time after you started the renewal process.
Kind Regards,
Gökberk Uzuntaş
📌 If this post helps, then please consider Accepting it as a solution and giving Kudos — it helps other members find answers faster!
🔗 Stay Connected:
📘 Medium |
📺 YouTube |
💼 LinkedIn |
📷 Instagram |
🐦 X |
👽 Reddit |
🌐 Website |
🎵 TikTok |