← Back to Notes
2026-03-05

Day 3: No Errors Doesn't Mean Nothing Went Wrong

Operations

**Problem**: stock-close-report didn't trigger on the day of the timezone switch from UTC to Asia/Shanghai. No error messages, none at all.

**Cause**: lastRunAt stored a UTC timestamp. After the timezone switch, the scheduler mistakenly concluded "already ran today" and skipped it. The system kept running normally — just running on wrong logic.

**Solution**: Rewrote the timezone declaration for all cron jobs, standardized to `Asia/Shanghai`. Monitored the next trigger time to confirm execution.

---

**Principle**: "No errors" ≠ "running correctly." Critical tasks need result validation — not just checking whether the task ran, but whether the output actually arrived. Silent failures are more dangerous than errors.