I'm running into a very twitchy SQL Server Agent bug. I don't have the time to spend pinning it down perfectly, but here's my best guess as to the scenario under which it occurs and two proposed workarounds that appear to work.
Scenario:
You have ba...