Context
Currently scheduled to run on 1st of each month at 8AM PST/9AM PDT:
|
on: |
|
schedule: |
|
# Scheduled to run at 4pm UTC (8am PST) on the first day of the month |
|
- cron: '0 16 1 * *' |
If this overlaps with a workflow schedule, it may prevent the workflow from running. keep-workflows-enabled disables the workflow for 5 seconds and if GH tries to schedule the workflow during that time, then it will not run. This is mostly not an issue if we miss one day and the workflow is scheduled to run daily. However, if the stars align and this happens to a weekly pathogen workflow, then the pathogen will not get updated for 2 weeks.
For example, the chikv workflow is scheduled at the same time and did not run as scheduled on 2026-09-01. I've manually triggered chikv, but we could consider how to prevent keep-workflows-enabled overlapping with the scheduled workflows.
Possible solutions
The easiest solution would be to schedule keep-workflows-enabled for 1AM PST/2AM PDT which is less likely to overlap with other schedules. There could be other fancy ways to query scheduled workflow times but probably not worth the effort here.
Context
Currently scheduled to run on 1st of each month at 8AM PST/9AM PDT:
.github/.github/workflows/keep-workflows-enabled.yaml
Lines 9 to 12 in b3274f4
If this overlaps with a workflow schedule, it may prevent the workflow from running.
keep-workflows-enableddisables the workflow for 5 seconds and if GH tries to schedule the workflow during that time, then it will not run. This is mostly not an issue if we miss one day and the workflow is scheduled to run daily. However, if the stars align and this happens to a weekly pathogen workflow, then the pathogen will not get updated for 2 weeks.For example, the chikv workflow is scheduled at the same time and did not run as scheduled on 2026-09-01. I've manually triggered chikv, but we could consider how to prevent
keep-workflows-enabledoverlapping with the scheduled workflows.Possible solutions
The easiest solution would be to schedule
keep-workflows-enabledfor 1AM PST/2AM PDT which is less likely to overlap with other schedules. There could be other fancy ways to query scheduled workflow times but probably not worth the effort here.