molecule-ai[bot] b83ddc7dff fix(scheduler): prevent NULL next_run_at from permanently dropping schedules (#722) ... Three bugs caused enabled schedules to silently disappear from the fire query (which requires next_run_at IS NOT NULL AND next_run_at <= now()): Bug 1 - fireSchedule() and recordSkipped(): when ComputeNextRun returned an error, nextRunPtr stayed nil and UPDATE SET next_run_at = $2 wrote NULL. Fix: change to COALESCE($2, next_run_at) so the existing DB value is preserved when $2 is NULL, and log the error explicitly. Bug 2 - org importer (handlers/org.go): nextRun, _ := ComputeNextRun(...) silently discarded the error. A bad cron expression would pass time.Time{} (zero value) to the INSERT. Fix: surface the error, log it, and skip the schedule INSERT via continue. Bug 3 - no startup repair: schedules already NULL'd by the pre-fix binary would never recover. Fix: Start() now calls repairNullNextRunAt() once on boot, recomputing next_run_at for every enabled schedule with a NULL value. Tests: TestFireSchedule_ComputeNextRunError, TestRecordSkipped_ComputeNextRunError, TestRepairNullNextRunAt_RepairsRows, TestRepairNullNextRunAt_DBError_NoPanic, TestOrgImport_ScheduleComputeError (all pass). Fixes #722 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>		2026-04-17 13:34:28 +00:00
..
scheduler_test.go	fix(scheduler): prevent NULL next_run_at from permanently dropping schedules (#722)	2026-04-17 13:34:28 +00:00
scheduler.go	fix(scheduler): prevent NULL next_run_at from permanently dropping schedules (#722)	2026-04-17 13:34:28 +00:00