You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"allow_concurrent_runs" should provide the possibility to kill the previous task, instead of just opening a new one or waiting. This is very useful for programs that continuously run (e.g. asking for user input).
As of now the only solution I found is manually terminating a run to allow for the new one in the queue to execute.
If applicable, add mockups / screenshots to help present your vision of the feature
This combination will allow not to wait for previous tasks before spawning the new one, but forced to reuse the terminal of the previous task, which should result in the previous terminal (and the task running in it) being killed, and the new task instantly started.
Check for existing issues
Describe the feature
"allow_concurrent_runs" should provide the possibility to kill the previous task, instead of just opening a new one or waiting. This is very useful for programs that continuously run (e.g. asking for user input).
As of now the only solution I found is manually terminating a run to allow for the new one in the queue to execute.
If applicable, add mockups / screenshots to help present your vision of the feature
"allow_concurrent_runs": "allow_multiple" | "wait" | "terminate"
The text was updated successfully, but these errors were encountered: