Manually running a pipeline randomly starts many instances at the same time

[mikeburek]

Randomly, when I manually run a pipeline, it will start about 5-7 instances of the pipeline at the same time. This has happened to coworkers, so it is not specific to my machine, such as any weird browser extensions or a mouse button that is going bad. This happens to me running it from my laptop or my RDP sessions to my jump box.

Between it all, I'm running Windows 10 and Windows 11, and only using Microsoft Edge for the browser.

For now, I set the concurrency to 1 so that when this randomly happens, so that I have a chance of canceling the last ones since they are queued while the first instance is running. This is very frustrating to open each extra instance and kill it, over and over. The speed of the monitoring webpage makes this even more frustrating.

[arindam006]

I am facing the same, have tried from different workspaces but nothing works for me, same behaviour in all different workspaces I had access to. I had deleted all browser data, tried from incognito, paused and restarted the fabric capacity but no luck.

Please let me know in case of any resolution / lead.

Probably a duplicate thread to this one.

[mikeburek]

Hi @v-tsaipranay, thank you for the private message to mark this solved. No, no solution has been found.

[v-tsaipranay]

Hi @mikeburek ,

We recognize that delays in finding a resolution can be challenging. Since the issue continues despite initial troubleshooting, moving forward with the Microsoft Support case is the best approach. Their team has access to internal tools, diagnostics, and environment-specific data that go beyond what community support can offer.

Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

Thank you.

[v-tsaipranay]

Hi @mikeburek ,

Thank you for posting in the Microsoft Fabric Community.

One possible cause is that multiple click events are being registered due to UI lag or delays in acknowledging requests, leading to multiple pipeline runs before the UI updates. Another possibility is a backend processing delay, where the system does not immediately reflect the pipeline execution status, prompting users to click multiple times.

To mitigate this, I recommend clicking the Run Pipeline button only once and waiting a few seconds before attempting another trigger. Additionally, you can monitor the Pipeline Runs section to confirm if a run has already been initiated before retrying.

Since you've set concurrency to 1, additional instances will queue up rather than run in parallel but cancelling them manually can still be frustrating. An alternative approach is to trigger the pipeline via Fabric REST API or Power Automate, which can help avoid UI-based triggering issues.

For more information on managing and monitoring pipeline executions in Microsoft Fabric, refer to the official documentation: Data pipeline runs in Microsoft Fabric, which provides guidance on how pipeline runs are handled, including manual execution and scheduled triggers.

Additionally, the article on Pipeline storage event triggers can help you understand how pipeline executions are triggered and managed. If the issue persists, I recommend capturing browser console logs (F12 > Console in Edge) or network traces to help diagnose the problem.

I hope this will resolve your issue, if you need any further assistance, feel free to reach out.

If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

Thankyou.

[mikeburek]

No, I'm clicking only once, and randomly multiple run instances happen. This has happened to me and other coworkers for months, across multiple computers, across multiple office and home locations, using multiple computer mice on the same computer. This is the only place, of all the websites and all the computer programs that multiple instances of something are being triggered by "one" mouse click.

Has no one else experienced this? Could there really be something at my company's network level that is randomly replaying only this click event?

This happens across multiple pipelines, large and small. It's always about 5-7 instances. It's never 2 or 3 instances.

[v-tsaipranay]

Hello @mikeburek ,

Apologies for the issue you have been facing.  When I tried to repro the scenario, the pipeline ran only once.

This might require a deeper investigation about your workspace, the pipeline details and the logic behind it to properly understand what might be happening. 

Please go ahead and raise a support ticket to reach our support team:

https://support.fabric.microsoft.com/support

If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

Thankyou.

[v-tsaipranay]

Hello @mikeburek ,

Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.

Thank you for your understanding and assistance.

[mikeburek]

No, no solution has been found.

[mikeburek]

It happens randomly, not every time. Across multiple users, across multiple computers, across multiple office locations, across multiple workspaces, across multiple pipelines, across multiple internet exit points.

[v-tsaipranay]

Hello @mikeburek ,

We apologize for the inconvenience caused. As mentioned in my previous post, I request you to raise a support case with Microsoft.

If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

Thankyou.