If a trigger goes missing in the database then we end up spamming the logs in QuartzSchedulerSPI.java:730.
We should not spam the logs. In addition, when this exceptional behavior occurs an admin should be made aware of change as this will affect the frequency at which a task is run. Triggers should not be missing so placeholder triggers will be created with a manual run frequency by default.
We could add a new system status check that reports if jobs are missing triggers/listeners or generically in error, then the error makes it to the user but does not build up GB of logs in a day. If we must leave the logging then recommend we consider the highest level instead of warn.