- Manual Trigger: Test the pipeline's functionality by manually triggering it.
- It works
- Trigger History: Examine the trigger's run history in detail for potential clues.
- Run history is fine, not scheduled trigger run history
- Pipeline Logging: Enhance logging configuration within the pipeline to capture execution details for analysis.
- Does not exectue from scheduled trigger so no logging.
- Trigger Logs: Analyze trigger-specific logs using Azure Monitor for insights.
- Does not execute from scheduled trigger so no logging
- DevOps Integration: Review DevOps release pipelines for errors in triggering or deployment steps.
- Devops release pipeline works
- Deployment Delays: Account for potential delays in pipeline activation after deployment.
- Waited a full day, did not execute
- Concurrent Runs: Check for restrictions on concurrent pipeline executions.
- No restrictions
- Gateway Configuration: Verify correct configuration of any self-hosted integration runtimes involved.
- Not using self hosted runtime, all done in ADF
- Permissions: Ensure that the ADF service principal has necessary permissions for trigger execution.
- What are the required permissions? How would I see the error? I just see nothing
- Caching Issues: Clear your browser's cache or try accessing from a different browser/incognito mode.
- Tried in Edge instead of Chrome, same problem
- Trigger Dependencies: Confirm that any external dependencies for the trigger are met.
- No trigger dependencies
- Azure Service Health: Check for known service issues affecting ADF.
- Azure health is ok
Azure Data Factory Trigger will not fire
I created a scheduled trigger for a pipeline in ADF, the pipeline is setup in Git and Devops to automatically deploy to the server on any change. It deploys successfully and the trigger is there, however when I go to "monitor" the scheduled trigger runs are empty. I have tried every increment, 15 minutes, hourly every 1 minute and nothing works. There no errors. I make sure the start date and time is back dated one day. What am I missing?
3 answers
Sort by: Most helpful
-
Andrew Hopkinson 6 Reputation points
2024-04-11T16:55:20.3133333+00:00 -
Andrew Hopkinson 6 Reputation points
2024-04-11T17:40:45.79+00:00 I think actually the problem is that Devops pipeline is saying that is completing but the trigger is not being published.
-
phemanth 15,160 Reputation points Microsoft External Staff
2024-04-12T03:07:54.8366667+00:00 Welcome to Microsoft Q&A platform and thanks for posting your question.
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: I created a scheduled trigger for a pipeline in ADF, the pipeline is setup in Git and Devops to automatically deploy to the server on any change. It deploys successfully and the trigger is there, however when I go to "monitor" the scheduled trigger runs are empty. I have tried every increment, 15 minutes, hourly every 1 minute and nothing works. There no errors. I make sure the start date and time is back dated one day. What am I missing?
**Solution:**Ok, I found the problem, you should add this to your trouble shooting, make sure that you have this line added to your Devops pipeline deployment:
TriggerPath: '$(Build.Repository.LocalPath)/trigger'
In addition, it seems to default to status of "stopped", so you will need to add a start task:
- task: toggle-adf-trigger@2 inputs: azureSubscription: 'xxxxx' ResourceGroupName: 'CNX-Core-DEV' DatafactoryName: 'CNX-DF-DEV' TriggerFilter: 'Hour Trigger Env' TriggerStatus: 'start'
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.
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
andYes
for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.