Context
Prompted by nextstrain/.github#153.
The only way I was able to see that workflows have not run is by toggling to the time-relative view and skimming down the page of all workflows. I would have continued to miss the workflows that have not run if I just scanned the list at the top of the page for failed workflows.
Description
It'd be helpful to flag pathogens that have not had a workflow run in a while. Ideally, this would parse the cron schedule from workflows and flag workflows that have not run at the scheduled time (with some margin). I'm not sure we want to dive into parsing the workflow contents for the cron schedule, so the simpler thing to do would be to flag any workflows that have not run within a hardcoded timeframe. Since our pathogens are scheduled to run daily or weekly, I think it'd be reasonable to check if the last run was within 8 days.
Context
Prompted by nextstrain/.github#153.
The only way I was able to see that workflows have not run is by toggling to the time-relative view and skimming down the page of all workflows. I would have continued to miss the workflows that have not run if I just scanned the list at the top of the page for failed workflows.
Description
It'd be helpful to flag pathogens that have not had a workflow run in a while. Ideally, this would parse the cron schedule from workflows and flag workflows that have not run at the scheduled time (with some margin). I'm not sure we want to dive into parsing the workflow contents for the cron schedule, so the simpler thing to do would be to flag any workflows that have not run within a hardcoded timeframe. Since our pathogens are scheduled to run daily or weekly, I think it'd be reasonable to check if the last run was within 8 days.