SQL Safe "missed backups" validation

I am curious, when SQL Safe determines there is a "backups did not start as scheduled" per the policy is it actually checking the VOLUME for the file, SQL Server's MSDB history, SQL Server job history, or the SQL Safe's internal Policy history?

 

What determines if a backup "did not start as scheduled"?