Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider adding timeout value to script execution #6076

nafai opened this issue May 8, 2024 · 0 comments

Consider adding timeout value to script execution #6076

nafai opened this issue May 8, 2024 · 0 comments


Copy link

nafai commented May 8, 2024

As seen in #2202, presenting in the agent console message Run commands can't execute, already busy.

By running a script that pauses for any reason (waiting on stdin, waiting on an interactive window, etc), an agent can get "stuck" and not process any other scripts you try to send it. An agent will remain in this state until the service is restarted, running agentupdate, etc.

Please consider adding a timeout value for script execution in config.json. Even a long timeout (1800/3600 secs as a default value) would be preferable to an indefinite timeout.

Alternatives could include adding the timeout as another field in the Run Commands dialog, or to just launch multiple scripts in parallel and not care if they ever finish executing.

@nafai nafai added the bug label May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

2 participants