mid.ssh.command_timeout_ms is not working as expected when executing ssh commands with Ssh rest via Mid serverIssue The mid.ssh.command_timeout_ms is set to 300,000 (3 minutes). When using the SSH REST to run a long-running shell command (5 minutes) via the MID server, the execution of the SSH REST stopped after 2 minutes, rather than the expected 3 minutes.CauseIn the SSH step, the mid.ssh.command_timeout_ms value is limited by mid.ssh.channel_timeout. The default value of mid.ssh.channel_timeout is 120,000 (2 minutes). mid.ssh.channel_timeout: Specifies the amount of time that the MID Server waits for activity on the SSH socket before closing the connection. If there has been no activity on the SSH socket for the specified timeout value, the MID Server closes the connection. Some devices, such as systems with embedded controllers like UPSs and PDUs, that have SSH enabled may require more time to respond to an authentication request. The channel timeout defines how long the channel can remain idle without receiving any output, while mid.ssh.command_timeout_ms defines the time allowed to receive the complete output.Resolution Set the mid.ssh.channel_timeout value to be greater than the mid.ssh.command_timeout_ms value. Related LinksThe mid.ssh.channel_timeout setting is only valid when the “Run for Long Time” option in the SSH step is disabled. MID Server parametersAdd a MID Server parameter