How to fix a scheduled trigger in Azure Data Factory that is not executing a pipeline?

Question

My scheduled pipeline trigger stopped executing an associated pipeline. I have already checked my resources, validated with no errors, and published the changes. The trigger had been working for months prior to this issue, and I followed all relevant documentation, but I still can't figure out what is wrong. How can I fix this problem?

Answer 1

hello Siphelele Hadebe

One possible reason could be that the trigger is not in the "Started" state. You can check the status of your trigger by using the az datafactory trigger show

If the status is "Stopped," you can start the trigger by using the az datafactory trigger start command.

Another possible reason could be that the trigger is not associated with the correct pipeline. You can check the association by using the az datafactory trigger show command and verifying that the pipelineReference section is correct.

If the above steps do not resolve the issue, you can try deleting and recreating the trigger.

Before deleting the trigger, make sure to stop it by using the az datafactory trigger stop command. Once the trigger is deleted, you can recreate it by following the steps in the documentation.

If none of these step's work, it's possible that there may be an issue with the Azure Data Factory service. I hope this helps.

Answer 2

The solution to this problem involved stopping the trigger, publishing the stopped trigger state change, restarting the trigger then publishing the started state change of the trigger.

I hope this helps!

Answer 3

Hi @Siphelele Hadebe
I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer .
Ask: My scheduled pipeline trigger stopped executing an associated pipeline. I have already checked my resources, validated with no errors, and published the changes. The trigger had been working for months prior to this issue, and I followed all relevant documentation, but I still can't figure out what is wrong. How can I fix this problem?
Solution: The solution to this problem involved stopping the trigger, publishing the stopped trigger state change, restarting the trigger then publishing the started state change of the trigger.
If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information.

I hope this helps!

If you have any other questions, please let me know. Thank you again for your time and patience throughout this issue.

---

Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.