Pipe line automatic trigger

[Shivani123]

Here’s a detailed message you can post in the forum:

Hi everyone,

I was using the pipeline, but unfortunately, it ran automatically without any scheduling or manual execution on my part. As a result, my allocated capacity was exceeded, causing issues.

I would like to understand why this happened and how to prevent unintended executions in the future. Has anyone else experienced this? Any guidance on troubleshooting or configuring the pipeline settings to avoid such occurrences would be greatly appreciated.

Thanks in advance for your help!

[Anonymous]

Hi @Shivani123 ,

Even if you have not explicitly set up triggers, there may be old or default triggers in the ADF that have not been deleted.
Check to see if there are triggers associated with pipelines (especially Schedule or Event-Based Trigger). Make sure that any unused triggers have been disabled or deleted. Also check if the pipeline may be called externally, e.g. REST API, etc.

For more details, you can refer to below document:

Data pipeline runs - Microsoft Fabric | Microsoft Learn

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.

[Shivani123]

I have checked and confirmed that there are no active, old, or default triggers in Microsoft Fabric, including Schedule or Event-Based Triggers. There are also no external calls, such as REST API requests, triggering the pipeline. However, the Microsoft Fabric Data Pipeline still ran continuously for nearly two days without sending any notifications or progress updates.