Hi @Jay ,
Thanks for your query.
The behavior is usually observed when we just stop the trigger and not publish it. Could you please confirm if you have published the trigger after stopping it? To double confirm on this, if you are using Code Repository, please change to Data Factory mode in UI and then go to Manage
tab and then Triggers
and see the actual state of the trigger you are having issue with.
In case if you have published the trigger and seeing this issue, then please do share below details for further analysis:
- Datafactory name & region?
- trigger name, type of trigger (schedule/tumbling window/event)?
- pipeline runID that was executed with this trigger run?
Looking forward to your response