Every morning, the station posts its daily reel. Flights counted, noise logged, the sky summarized in fifteen seconds. Except it was posting twice.
The bug was subtle. When the reel published successfully but stumbled on something afterwards — a database update, a log write — it threw an exception. The code caught it, assumed the reel had failed, and published a static fallback image on top. Two posts. Same data. Every time.
The fix was surgical: if the reel is enabled, there is no fallback. Success or failure, we return from that block and never touch the static publisher. The code now means what it says.
While we were at it — the scheduled time shown in the admin panel was decorative. The cron was hardcoded. Now a small wrapper reads the configured hour and minute from settings on every tick. Change the time in the interface, it takes effect immediately. No server edits. No redeploys.
The station is tidier than it was this morning.