Well no, a restart won’t stop the action itself. It will just indicate to the BigFix client running on the targeted computers that those computers need to be restarted.
There might perhaps be some kind of network issue between the server and the clients that may cause them to be restarted after a prolonged delay or indeed not at all. For example some clients can become unresponsive or “non-reporting” when such a network issue occurs, meaning that the client is not reporting back to the server at regular intervals and so it is not aware that there is any work for it to do (under normal conditions, clients essentially “download” the action from the server and process it. So if it can’t contact the server, it cannot perform the action).
One option might be to automatically exclude non-reporting endpoints from the list of targets - there is a checkbox that can be checked on the “Settings” tab on the plan definition to achieve this. Please see the Excluding non-reporting endpoints page for more details on how to use this feature.
If that doesn’t help though, there’s a reasonable chance that you may need to engage IBM BigFix support directly to troubleshoot exactly what the issue might be if some of your clients are not processing actions correctly, Depending on what the cause is, it can be tricky to get to the bottom of it so it’s not really practical to try to do that via a forum post. From the Server Automation point of view though, it’s main job is to orchestrate and coordinate the work on the endpoints, however if an endpoint is not properly processing the work it has been given, then that goes a little bit outside our domain and into the domain of the BigFix client itself.