scheduler check should (un)schedule grouper loader other job changes

I added an other job to database configuration.  then i ran the scheduler check.  it didnt schedule this job.  i started a daemon, then it scheduled it.

Would be nice to move in the direction where restarts (or just starts) arent required when changes to configs happen. Wonder if the scheduler daemon should do this (runs every 30 minutes), but also in the UI when the loader config is changed by the UI or import in UI, it could call the method too so the user doesnt have to wait 30 minutes?