Hmm.. The only thing I can think of offhand is that maybe there is an orphaned job stuck in the collector/Job Engine v2 database. I recommend following the steps outlined in the KB article below to clear out this temporary database. Post back and let us know if this does or does not resolve the issue.
