Would like to be able to queue a second action against a host after power change.
Example: If I power on a host and want to deactivate it, I have to wait for it to fully turn on before I can request to deactivate it. This works ok in reverse as deactivate is fast but if forgotten it takes a bit to be usable, I've seen 20 minutes after it shows on and available.
At the moment if I power on the other actions are not usable
Would like to be able to queue them instead so I don't have to wait for the task to finish before pressing the next button. The oh I forgot to deactivate or oh I need to turn that off after accidentally turning it on etc... turn into a longer process.
I have not run into this being a nuisance other than power on/off but if it applies elsewhere then it would make sense to apply it there as well.
Request: Queued actions after power on/off QOL
3
I've seen this similarly after running a scripted action. If I forgot to deactivate the machine first or wanted to run 2 scripted actions instead of the 1 I kicked off, I'm "stuck" waiting for the first scripted action to finish (or try to cancel it) before I'm able to do anything.
Like Tomas is saying, it'd be nice to be able to queue up a task/next thing to do once the current task/scripted action is complete.
Please sign in to leave a comment.
Comments (1 comment)