topic Re: Pipeline Ran in its Own - Need Help in Pipelines

Pipeline Ran in its Own - Need Help

Akshy — Fri, 21 Feb 2025 05:16:25 GMT

Hey folks,

So, my pipeline decided to run all by itself without any scheduling or me hitting the "go" button. Ended up blowing past my allocated capacity and causing a bit of a mess.

My F64 capacity has completed within a few hours.

Anyone else faced this? I’m trying to figure out why this happened and how to stop it from running wild in the future. Any tips on settings or troubleshooting would be super helpful!

I don't know why this much bugs or issues are there in fabric it causing a lot of issues to all

Re: Pipeline Ran in its Own - Need Help

Anonymous — Fri, 21 Feb 2025 09:11:01 GMT

Hi Akshy ,

Pipelines can be triggered by old undeleted triggers or default triggers, even if you do not explicitly set the trigger. For example, in the pipeline run history, look at the parent pipeline or activity that triggered the pipeline or other external tools that were called.

Best Regards,
Adamk Kong

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

Re: Pipeline Ran in its Own - Need Help

Akshy — Mon, 24 Feb 2025 01:07:47 GMT

Hi Sureshvarma

Hey, thanks for the solution! It was really helpful. Normally, we have used 20 workspaces, but out of them, 4 were scheduled by default during creation, and we forgot to change the settings, which led to the pipeline running automatically. One of these workspaces was scheduled for two days, another for three days, and so on.

Since the default configuration cannot be changed, I deleted the affected workspaces and created new ones with the correct settings. Everything is working fine now. Going forward, we need to check each workspace after creation to ensure it's configured correctly.

Re: Pipeline Ran in its Own - Need Help

Sureshvarma — Mon, 24 Feb 2025 02:06:27 GMT

Hi Akshy

This issue sometimes occurs due to improper workspace configuration at a higher level.

When creating a workspace, ensure that the default triggers or scheduling settings are not applied. If these settings are automatically assigned by default, they cannot be modified later. In such cases, the best approach is to delete the workspace and create a new one with the desired configurations