It stands to reason that amongst the nodes and triggers in Environment Manager there need to be some timeout settings configured, otherwise a badly-configured condition or action could cause your users to be waiting an awful long time for certain things to happen, like logon or process start. And as we all know, the user experience is what matters.
If a timeout limit is exceeded, the configuration element still runs to completion, but it is considered failed and therefore child nodes will not run. The default values, in milliseconds, are set under the following Registry keys and can be altered to suit your own needs.
HKLM\Software\AppSense\Environment Manager
The default setting for a trigger is infinite, but given that triggers contain nodes and the timeout for each node is finite, this means that the trigger cannot execute indefinitely. That is, unless you set the NodeTimeout to Infinite as well, which would definitely not be a action I would recommend.
The only time these timeouts are overridden is if you configure a Custom action with its own timeout. Timeouts in Custom actions will override the default node setting (see image below for an example of a Custom action with timeout). With this in mind, setting the Custom action timeout to 0 (infinite) could possibly cause a node to execute for a very long time, and should probably be avoided.
It is unlikely that you will need to alter the timeout settings from the default, but in the event that you do encounter a situation where it is required, then these Registry settings will allow you to do so.
Share
