Yes, that’s what I mean, the actionscript command restart or restart <seconds> are the correct way to handle restarts within a baseline. That informs the client that a reboot is happening, so the client should stop executing actions at that point and should resume after the reboot.
The ‘pending restart status is not cleared after a reboot’ is a very common issue. When the client starts, it checks several different areas to determine whether there are any indications a reboot is still needed. If any are needed, the ‘Pending Restart’ flag is not cleared for any action statuses. Sometimes badly-designed software updates the PendingFileRenameOperations key on every startup, and the presence of values in that key prevents any Pending Restarts from being cleared. We describe the behavior, and client settings to exclude entries from the list we search, at Determining if a restart is needed - Customer Support
As a worst-case, we describe a value that will ignore all PendingFileRenameOperations values when calculating whether a restart is needed, at List of settings and detailed descriptions -
With the setting _BESClient_ActionManager_PendingRestartExclusions=:; all entries in the Microsoft registry key HKLM\System\CurrentControlSet\Control\Session ManagerPendingFileRenameOperations are ignored because every entry is a path containing always a colon.
However, none of this ‘Pending Restart / Pending Restart Not Cleared’ would cause the later fixlets to show the status ‘Not Relevant’ on the Console result. I think we’d need to get more details on the relevance of the Baseline, those individual Components, and the Action Settings you used when sending the action.