Interval cron trigger not triggering as often as expected
See original GitHub issueDescribe the bug I have an action that should be running every 5 minutes, which is the maximum amount of times an hour according to docs. Therefore, there should be 12 events per hour in an ideal run. I am getting 2–4 events per hour.
Unclear if this is an issue with the frequency or with an interval cron setting as a whole. Actions at a defined time (ie - cron: '0 7 * * *'
) work perfectly in the same repo.
To Reproduce
on:
schedule:
- cron: '*/5 * * * *'
Expected behavior Action is triggered roughly every 5 min.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:5 (1 by maintainers)
Top Results From Across the Web
airflow cron schedule interval not triggering DAG properly
I've just tested with the latest version of croniter (used by airflow) and it seems to work as expected, nevertheless the leading 0....
Read more >CRON Scheduled automation not triggering
Solved: Hi, Can someone help me, why is the automation not triggering, I've been testing this today (01/04/2022), matching the trigger to ...
Read more >Scheduled pipeline suddenly not triggered anymore (cron)
Hi,. Our pipeline is scheduled to run every night. I have checked: no change in the yaml-file for a long time - can't...
Read more >Top Reasons Your Cron Job Isn't Running
This article walks through the most common reasons why your cron job may not be working as expected: schedule errors, environmental changes, ...
Read more >Why is my crontab not working, and how can I troubleshoot ...
This is crontab's attempt to try to "do what you want" when the time changes out from underneath it.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
According to https://docs.github.com/en/actions/reference/events-that-trigger-workflows#scheduled-events
Also, the schedule run might get delayed if the actions service is under DDOS attack. 😞
I am going to close this since the schedule is controlled by the service, if you have lots of missing runs for schedules, please reopen this with some sample data (repo URL + time interval), I can help you check our telemetry.
The exactly same problem here as well 😦