Sounds like a bug.

Is this the first time the job was run? Have you checked the raw data in the msdb tables?