Agree with orbiton, check that the machine actually did restart by checking the ‘boot time of operating system’ relevance or ‘System Boot Time’ property.
If the machine actually did reboot as scheduled, but still appears to have ‘Pending Restart’ after rebooting, you may be encountering an issue where we don’t detect the ‘pending restart’ has completed because of badly-implemented software that writes to the PendingFileRenameOperations registry key. This causes a false detection of ‘Restart Required’ by BESClient, and when we think a restart is still required it does not clear any of the actions’ Pending Restarts.
You can configure the BESClient to either ignore some of the PendingFileRenameOperations values, or all of them, see Baseline Fixlets having "true" in there relevance become not relevant after restart