Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Don't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.

Reply
mh20221111
Frequent Visitor

Multiple updates are triggered by a single scheduled execution

When scheduling daily updates in PBI dataflow, the processing history sometimes shows multiple processes running simultaneously, especially when there is a large volume of data.

One process finishes after the update, while the other continues running indefinitely and shows "Cancelled" after 25 hours.

What could be the cause of these events? Does it appear that multiple processes are running on the update history, but in reality, only one process is actually running?

log.jpglog2.jpg

1 ACCEPTED SOLUTION
v-achippa
Community Support
Community Support

Hi @mh20221111,

Thank you for reaching out to Microsoft Fabric Community.

 

For the above issue please follow the below solutions:

  • If the same dataflow is scheduled to update at close intervals or has overlapping schedules, power bi might mistakenly trigger multiple processes simultaneously. Review all scheduled refresh times for the dataflow. Ensure there is only one schedule per dataflow and no overlapping or duplicate schedules exist. Ideally, set updates at non-overlapping intervals.
  • Long-running updates due to large datasets or complex transformations can cause the next scheduled update to overlap with the previous one. Use incremental refresh to process only new or updated data instead of the entire dataset. This reduces processing time and prevents overlapping processes.
  • Power BI may retry failed updates automatically, which can create duplicate processes if the original update is still running. Implement incremental refresh for your dataflow to limit the amount of data processed in each update.
  • Do not manually trigger an update close to a scheduled update time. If needed, ensure the schedule is paused temporarily.
  • If the dataflow depends on other linked dataflows, ensure the refresh times are arranged properly so that linked dataflows finish before dependent dataflows begin.
  • If you are on a shared capacity workspace, consider upgrading to Power BI Premium (Per User or Dedicated) to handle heavy data transformations.

By following the above solutions it prevents overlapping processes and improve the overall efficiency of Power Bi environment.

 

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

 

Thanks and regards,

Anjan Kumar Chippa

View solution in original post

4 REPLIES 4
v-achippa
Community Support
Community Support

Hi @mh20221111,

Thank you for reaching out to Microsoft Fabric Community.

 

For the above issue please follow the below solutions:

  • If the same dataflow is scheduled to update at close intervals or has overlapping schedules, power bi might mistakenly trigger multiple processes simultaneously. Review all scheduled refresh times for the dataflow. Ensure there is only one schedule per dataflow and no overlapping or duplicate schedules exist. Ideally, set updates at non-overlapping intervals.
  • Long-running updates due to large datasets or complex transformations can cause the next scheduled update to overlap with the previous one. Use incremental refresh to process only new or updated data instead of the entire dataset. This reduces processing time and prevents overlapping processes.
  • Power BI may retry failed updates automatically, which can create duplicate processes if the original update is still running. Implement incremental refresh for your dataflow to limit the amount of data processed in each update.
  • Do not manually trigger an update close to a scheduled update time. If needed, ensure the schedule is paused temporarily.
  • If the dataflow depends on other linked dataflows, ensure the refresh times are arranged properly so that linked dataflows finish before dependent dataflows begin.
  • If you are on a shared capacity workspace, consider upgrading to Power BI Premium (Per User or Dedicated) to handle heavy data transformations.

By following the above solutions it prevents overlapping processes and improve the overall efficiency of Power Bi environment.

 

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

 

Thanks and regards,

Anjan Kumar Chippa

Hi @mh20221111,

 

Thank you for reaching out to Microsoft Fabric Community.

 

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution i have provided for the issue worked? or let us know if you need any further assistance?
If my response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

 

Regards,

Anjan Kumar Chippa

Thank you for your response. I have confirmed with my team members, and we understand that this issue corresponds to the third point you mentioned: "Power BI may retry failed updates automatically, ...".

And we recognize that similar incidents may occur in the future.

3CloudThomas
Super User
Super User

You need to open a support case with Microsoft to find out the issue.

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.

Feb2025 Sticker Challenge

Join our Community Sticker Challenge 2025

If you love stickers, then you will definitely want to check out our Community Sticker Challenge!

Jan25PBI_Carousel

Power BI Monthly Update - January 2025

Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.

Jan NL Carousel

Fabric Community Update - January 2025

Find out what's new and trending in the Fabric community.