Dataflow running late

[brunoctesser]

Why is my dataflow running late (scheduled to run at 6PM but only ran at 7PM, for instance)?

I have no other dataflows scheduled. This one ingests data coming from only 6 views in a local DB2 database, which are not very big anyway. There are no transformations besides the "source" and "navigation" ones, as all the transformations were already made in the database views. I'm on a Premium per User License. 

The problem is not the duration time for the refresh, but the fact that it runs late. I've tried looking it up online, but could not find any answers.

Thanks in advance.

[V-yubandi-msft · Accepted solution]

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!   

[brunoctesser]

Hello @V-yubandi-msft , thank you for your response.

Is DirectQuery for Dataflows available to premium-per-user subscriptions/workspaces?

I can't seem to make it work.

[brunoctesser]

@V-yubandi-msft Forget it, I turned enchanced compute engine on and it worked! Thanks!

[rohit1991]

Hi @brunoctesser 

To address dataflow running late:

Possible Causes:

1. Capacity Overload: Shared capacity in Premium may cause delays.
2. Batch Scheduling: Power BI schedules in batches, causing slight delays.
3. Source Delays: Network latency or DB2 query delays.
4. Dependencies: Linked dataflows or datasets causing refresh delays.

Solutions:

1. Check Logs: Review refresh history for delays.
2. Optimize Source: Ensure the DB2 database has no latency issues.
3. Adjust Schedule: Shift to a less congested time slot.
4. Monitor Capacity: Verify Premium capacity usage in Admin Portal.

[uzuntasgokberk]

Hello @brunoctesser ,

Could you please check timezone?

Best Regards,
Gökberk Uzuntaş

LinkedIn: https://www.linkedin.com/in/g%C3%B6kberk-uzunta%C5%9F-b43906198/

Medium: https://medium.com/@uzuntasgokberk

İf this post helps, then please consider Accept it as solution and kudos to help the other members find it more quickly.

[brunoctesser]

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. 

[uzuntasgokberk]

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.

Best Regards,
Gökberk Uzuntaş

LinkedIn: https://www.linkedin.com/in/g%C3%B6kberk-uzunta%C5%9F-b43906198/

Medium: https://medium.com/@uzuntasgokberk

İf this post helps, then please consider Accept it as solution and kudos to help the other members find it more quickly.

[brunoctesser]

@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.

[uzuntasgokberk]

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 .

Best Regards,
Gökberk Uzuntaş

LinkedIn: https://www.linkedin.com/in/g%C3%B6kberk-uzunta%C5%9F-b43906198/

Medium: https://medium.com/@uzuntasgokberk

İf this post helps, then please consider Accept it as solution and kudos to help the other members find it more quickly.

[uzuntasgokberk]

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.

Best Regards,
Gökberk Uzuntaş

LinkedIn: https://www.linkedin.com/in/g%C3%B6kberk-uzunta%C5%9F-b43906198/

Medium: https://medium.com/@uzuntasgokberk

İf this post helps, then please consider Accept it as solution and kudos to help the other members find it more quickly.

[brunoctesser]

It was a scheduled refresh. "Agendado" means scheduled. I will follow your advice and open a ticket, thank you very much!