Custom Actions cause Environment Manager to hold logoff until completion/timeout reached

Version 1

    Verified Product Versions

    Environment Manager 8.6Environment Manager 8.5Environment Manager 8.4Environment Manager 8.2Environment Manager 8.1Environment Manager 8.3


    When attempting to log off an endpoint whilst a Custom Action script is still running and the timeout has not yet been met, the logoff is stalled until completion/timeout, rather than being forcibly closed by the logoff process.
    When the Custom Action script is executed, Environment Manager honours the timeout value even when a logoff is initiated.


    EXAMPLE: A script is executed to display a message box with a timeout of 0 (zero), and the user attempts to logoff.  The logoff would then stalled indefinitely until the message box is closed.

    This behaviour is by design as Environment Manager is honouring the timeout value as defined in the configuration.

    As an alternative, if you configure a Custom Execute action to call the script instead. The script will then be executed outside of the agent and if it is still running when the user attempts to log off, the scripting engine will be forcibly closed.

    NOTE: The alternative of calling a script via a Custom Execute action should only be implemented if it does not matter if the script completes or not.