So the job ran every time up until 2/21? And you confirmed that the job wasn't already running at that time? Is the schedule for the job enabled (disabling the schedule won't update the modified date for the job)?
I already verified those details. As mentioned the SQL job is enabled. Is there a way if I can find out if the SQL job was disabled by some user at that time..since you mentioned that disabling a job won't affect the modified date which makes sense because you are not making changes to it. Can I find this info in the default trace file or any other way of grabbing that info.
Disabling the job and disabling the schedule are two different things, which is why I asked. The job can be enabled while the schedule that runs it is disabled. Disabling the actual job will update the modified date.
Apologies I misread that in a hurry. However, both of them are enabled. I will revise my question is there a way to find out if someone disabled the schedule and then re-enabled it as it won't affect the modified date.
Unfortunately, that information isn't logged by default.
Other questions:
Was SQL Agent running at the time? (it probably was, but should be asked)
Did you confirm that the schedule isn't set to skip that day for some reason or that it has an end date set that would've caused it to miss?
When you look at the job history for the job can you confirm it was previously invoked by the schedule?
All the other jobs are running as scheduled at the right time(s)?
We'd similar issues as you posted, but what happened to us, unfortunately we'd changed the order of the sequence of steps. This was caused our job to skip the executions for particular steps. Later we'd changed it to default, it was fine.