# \`convox app cancel\` does not work, says "unimplemented"

**URL:** https://community.convox.com/t/convox-app-cancel-does-not-work-says-unimplemented/550
**Category:** Rack (Version 2)
**Created:** [June 7, 2019, 10:15pm UTC](https://community.convox.com/t/convox-app-cancel-does-not-work-says-unimplemented/550 "2019-06-07T22:15:10Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![xtagon](https://avatars.discourse-cdn.com/v4/letter/x/c37758/32.png) [@xtagon](https://community.convox.com/u/xtagon)
#### Post date: [June 7, 2019, 10:15pm UTC](https://community.convox.com/t/convox-app-cancel-does-not-work-says-unimplemented/550/1 "2019-06-07T22:15:10Z")

</div>

Any time my local rack app gets stuck in an “updating” state, which happens when iterating on getting things working in the Dockerfile and convox.yml with my app, there is no way to cancel it and start over without deleting the app and re-creating the environment variables and rebuilding the image.

```auto
$ convox apps cancel
Cancelling my-app... ERROR: unimplemented

$ convox apps 
APP STATUS RELEASE   
my-app updating RMUSJORMGT

```

Is `convox apps cancel` just not implemented in Local? What is the recommended solution?

I can run `convox start` again without cancelling, but doing so often leads to errors such as this one, which I think may be related: [ERROR: dial tcp: lookup api.convox.svc.cluster.local: too many open files](https://community.convox.com/t/error-dial-tcp-lookup-api-convox-svc-cluster-local-too-many-open-files/505/2)

My theory is that the app’s state being stuck in “updating” and re-running is trying to run one instance on top of the other instead of cancelling it?