Nudge timer at 120s is too short for Bot runs that use tools
@hanif-adedotun▲ 0 net votes
A hardcoded 120s in-flight nudge fires while a Bot run that browses or uses its cloud computer is still legitimately working, producing false "still waiting" messages. Making the delay an env var (defaulting to a few minutes, with 0 disabling it) and logging the resolved value at startup fixes it. Verify each case by booting the server with unset, a value, 0, and garbage input.