logo
PricingBlogDocs
Runops Docs
s3-storage
aws-secrets-manager
architecture
templates
enhanced-security
execution-review
manage-credentials
create-users
webhooks
pci-dds
soc2
self-host
runtime-information
github-integration
access-control
portal
directory-service
command-line
manage-users
multiple-agents
hashicorp-vault
secrets-manager
request-access
slack-automation
link-automations-connection
rich-automation-inputs
session-recording
proxy
templates-access-control
GDPR
collaborative-automations
security
kill-task
privacy-policy
faq
slack
portal
command-line
User Guides
12aws-ecs-exec
08python
11kubernetes-apply
09kubernetes
02postgres
Heroku
14rails-console-k8s
03mssql
13rails-console-ecs
15vault-cli
05shell
06node
index
sqlcl
04mongo
10kubernetes-exec
cqlsh
07elixir
01mysql
kubernetes
heroku-oneoff
ecs
index
heroku-rproxy
saas
eks
index
aws
authentication
endpoints
index
windows-powershell
troubleshooting
windows-docker
windows-wsl
macos
index
reuse-secrets
Runops Proxy
Runops Docs

kill-task

Kill Tasks

If the command is taking to long, it’s possible to kill an existent task in a running state. However, it is not guaranteed that it will succeed.
plain text
runops tasks kill --id <task-id>
Then, issue a get task to see if the task changed its state to killed:
plain text
runops tasks get --id <task-id>
security
privacy-policy

Powered by Notaku
Helpful?
Share
Content
kill-task
Kill Tasks