Your environment
Let us know details such as

• Carnegie Mellon's Autolab at https://autolab.andrew.cmu.edu/
• RHEL 8

Steps To Reproduce
Steps to reproduce the behavior:

1. Define a new scheduler job with the action field containing a value that does not match an existing filename
2. Save it
3. Watch the exceptions start to be generated every [INTERVAL]

Screenshots

Date: Tue, 03 Sep 2024 07:08:08 -0400
Subject: [CMU-Autolab-Prod Error]  (LoadError) "cannot load such file -- /opt/autolab/courses/[REDACTED].r...
A LoadError occurred in background at 2024-09-03 07:08:08 -0400 :
-------------------------------
Backtrace:
-------------------------------

  /opt/autolab/app/controllers/application_controller.rb:281:in `require'
  /opt/autolab/app/controllers/application_controller.rb:281:in `block (3 levels) in run_scheduler'

Suggestions

• Validations could require the action to be an existing file
• The controller could require that a successful visual run occur before the job can be enabled
• The scheduler could auto-disable or do exponential back-off for failing jobs.
  cannot load such file -- /opt/autolab/courses/[REDACTED].rb
  /opt/autolab/app/controllers/application_controller.rb:281:in `require'
• if nothing else, scheduler errors that are likely to be course errors could be caught and logged but not passed to exception notifier