Reputation: 1
I've created a simple pipeline with a number of copy activities. When I attempt to debug or "trigger now" the pipeline starts executing and then after about a minute, a message flashes, and another instance of the pipeline starts.
Message Screenshot:
Anybody experience this or know how to prevent it?
Upvotes: 0
Views: 1136
Reputation: 733
Please check the trigger definition, below is a sample trigger.
In this you can set the trigger schedules.
In your case, I think the Recurrence is Every 1 Min(s).
You can change it according to your use case.
Thanks!
Upvotes: 2
Reputation: 16431
As a supplement, you could go to Monitor-->Pipeline run-->Trigger/Degbug to check the pipeline run history.
Then you could know how the pipeline runs, manual debug(triggered) running or trigger triggered.
Then remove the trigger related like @HimanshuSinha-msft said.
Also please make sure you are the only one who operate the pipeline in the current time and the pipeline is not triggered or called by other services or executed by other pipeline actives, , such as logic app, etc..
HTH.
Upvotes: 0
Reputation: 1806
What happens when you just do a debug ? I think you have two triggers whcih are associated and so when you do "trigger now" both of them are getting fired . May be the below screenshot help to check that .
Upvotes: 0