Azure Devops scheduled pipeline does not trigger

user_987925 0
Viewed 1752

I have the following configuration: Azure DevOps Server Version Dev18.M170.8

trigger: none # No CI build
pr: none # Not for pull requests

schedules:
- cron: "* * * * *"
  displayName: Every minute build
  branches:
    include:
    - master
  always: true
  
jobs:
- job: RunMyCustomTask
  pool: 'DedicatedPoolWith1Agent'
  condition: always()
  steps:
  - task: mycustomtask@0'

The pipeline is created for a separate repo and has a dedicated agent pool. It should run, normally, every minute, based on the configuration. This is critical for me. I can change to every 2 minutes or 5 minutes, but it does not matter, it must be scheduled precisely at the right intervals.

Now, I have the issue that the pipeline is scheduled every minute, and then, for no whatsoever reason, it is not scheduled anymore. I have checked this during a day, and it happened that it wasn't scheduled for 6 minutes the most. I do not understand why this is happening. Any ideas or suggestions? I need schedules to be guaranteed. Trigger and pr: none makes no difference, with or without them. Image example: scheduled pipeline not executing 6 minutes

Agent execution logs

azure-pipelines jobs azure-devops scheduled-tasks cron
1 Answers

I'm not sure that Azure DevOps pipelines is the appropriate place to be running frequent, short-lived processes on a short timer.

The documentation even states that there is a limit of about 1000 jobs per week: https://docs.microsoft.com/en-us/azure/devops/pipelines/process/scheduled-triggers?view=azure-devops&tabs=yaml#limits-on-the-number-of-scheduled-runs

There are certain limits on how often you can schedule a pipeline to run. These limits have been put in place to prevent misuse of Azure Pipelines resources - particularly the Microsoft-hosted agents. This limit is around 1000 runs per pipeline per week.

Based on your statement, it must be scheduled precisely at the right intervals, I'd reconsider whether pipelines are the right tool for this job. There is no real-time guarantee with scheduled pipelines.

user_7817540
Related