I was pulling background data from a job in PowerShell, and it kept coming up short from the same, final section of data that I just KNEW should be there.

Fiddled with the primary application for hours... HOURS! Then, I checked the log. There it was in all its Glory, tee'd out to the log during job execution.

What. The. Shit.

So, it seems that, since I was asynchronously pulling data in a loop keyed to the job status and had inserted a little sleep statement in the wrong place, I'd been missing the last second's worth of data. You just couldn't tell most of the time.

Nice.

5 minutes later it was working fine with a new loop/control structure. Jesus.