Something I wanted to clarify about this:
This timeout should not depend on how long the action takes to execute, but how long a specific
run command takes to execute. You could have a baseline or an action that takes 5 hours to run for some unknown reason, but as long as no single command takes more than 2 hours to run within that execution, then the timeout should NOT be triggered.
This is again why I emphasize, that the timeout should always be set to something, it is just a matter of how long. 1 hour, 2 hours, 6 hours, SOMETHING.
Generally if you are going to run a background long running process with BigFix, then it is best to trigger it with a “run” command and let BigFix move on to other actions. (you have to be careful with this kind of thing, not run it in the __Download folder, etc…) So even in cases where you might run a background AV scan, I would highly recommend kicking it off with bigfix, then gather the results later with a separate action, or just analysis.