Manual mute/unmanage action fails for all nodes and users with "Unmanage now failed" and "Mute now failed" messages

This is a known issue that can occur when a user accesses the SolarWinds web console from a remote host and there is a time synchronization discrepancy between the remote host and the primary SolarWinds Platform server. Even a small difference, where the remote server time lags behind, can cause manual "Unmanage Now" and "Mute Now" actions to fail.

The issue occurs when a user accesses the SolarWinds web console from a remote workstation and there is a slight time synchronization discrepancy between the remote system and the SolarWinds Platform server.  This behavior is associated with sensitivity to timestamp differences between the client initiating the action and the SolarWinds Platform server processing it. As a result, manual mute and unmanage operations may fail when performed from remote hosts.

As an initial step, verify and correct any time synchronization issues on the SolarWinds Platform server. The SolarWinds Platform server's date and time should not lag behind the remote workstation being used to access the web console. Time zone differences are not a concern, only the actual date and time synchronization matters.

If time synchronization does not resolve the issue, use the Schedule Maintenance option instead of Unmanage Now or Mute Now. Alternatively, perform the action from the Manage Entities page. 

NOTE: This has been identified as a known issue, and a fix is planned for a future release of the SolarWinds Platform.