Result of the specific PowerShell query in pattern's step is not returned, and step always finishes in 80s Issue Some specific patterns run PowerShell command and executes it on the target device. If the execution takes longer than 80 seconds (default) no output will be returned and in the Horizontal discovery log, we can see an empty Command response like in the picture below. ReleaseAnyCauseThis behaviour is controlled by MID server property - sa.local_command_timeout_ms. If the PowerShell query requires more time, result will not be returned. ResolutionIn order to increase the timeout and have the result of the PowerShell query returned, create and set a value for MID server property sa.local_command_timeout_ms on a higher value than PowerShell scripts needs for execution. Example: If the query takes 150 seconds to complete running from PowerShell console, set sa.local_command_timeout_ms property to 160.