We decided that a cron-scheduled GitHub Actions workflow should not be active at this time, but might be in the future. Accordingly we renamed the fail with the suffix ‘.inactive’, which has been our routine method for putting a workflow ‘on hold.’
Surprisingly, the scheduled execution is still occurring. Do scheduled jobs make their way into the crontab of runners directly, and stay there until/unless they are actively located and removed? We can’t explain this behavior.