Greg Dodd shows how you can control the number of history records for SQL Agent jobs:
Looking at the Job Activity Monitor, I could see that the Last Run was Saturday morning, and the output of the job was there, I knew that the job was running, but when viewing the Agent History, it showed no history.
Digging further, I noticed that it wasn’t just the history of this job missing, but almost all jobs were missing their history or only had 1 or two runs in them.
Read on to find out what happened. Setting Agent job history limits is important, but you also have to leave enough records on there to diagnose issues.