Today we caught a silent killer in our automation stack. Seven daily maintenance jobs--including analyze_topic_gaps and detect_duplicate_posts --had stopped firing for nearly four days, while sub-hour jobs continued to run without complaint. The issue lived in the scheduler: register_job was attaching an IntervalTrigger without a next_run_time , so every worker restart forced the 24-hour cadence to re-anchor to boot time. This meant under active development with frequent restarts, the job's next fire was perpetually pushed past the latest boot and never ran. We fixed it by anchoring those interval jobs to the persisted plugin_job_last_run_<name> epoch, ensuring they resume correctly after a restart instead of relying on the process clock. (PR #797) The rest of the day was spent completing the site_config constructor-DI migration.…