# API: alloc stop doesn't stop per documentation

**URL:** <https://discuss.hashicorp.com/t/api-alloc-stop-doesnt-stop-per-documentation/35123>\
**Category:** Nomad\
**Created:** [February 2, 2022, 1:23pm UTC](https://discuss.hashicorp.com/t/api-alloc-stop-doesnt-stop-per-documentation/35123 "2022-02-02T13:23:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![c.k](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/c.k/32/16109_2.png) [@c.k](https://discuss.hashicorp.com/u/c.k)\
**Post date:** [February 2, 2022, 1:23pm UTC](https://discuss.hashicorp.com/t/api-alloc-stop-doesnt-stop-per-documentation/35123/1 "2022-02-02T13:23:54Z")

</div>

I am developing an internal mechanism to remotely stop allocs via the Nomad API. In my testing, I have noticed that using a POST on /v1/allocation/:alloc\_id/stop does in deed stop the specific alloc, but it starts it on the same node (below screenshot shows this). Is the documentation incorrect ([Commands: alloc stop | Nomad by HashiCorp](https://www.nomadproject.io/docs/commands/alloc/stop) → “…allows a user to perform an in-place restart…” The restart command says the same thing. The nomad GUI says this for the stop command → “This will reschedule the allocation on a different client.”) or is the API incorrect or is there something that I am missing? Thank you as always!

 ![image](https://global.discourse-cdn.com/hashicorp/original/3X/a/a/aa9f5a08e1508027ca581e95355eb9359a4bba4d.png)

---

<div class="post-metadata">

**Author:** ![jrasell](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/jrasell/32/5500_2.png) [@jrasell](https://discuss.hashicorp.com/u/jrasell)\
**Post date:** [February 2, 2022, 1:30pm UTC](https://discuss.hashicorp.com/t/api-alloc-stop-doesnt-stop-per-documentation/35123/2 "2022-02-02T13:30:14Z")

</div>

Hi @c.k. I believe both documentation items are incorrect for different reasons. The API does not allow for an in-place restart, it allows a user to stop an allocation which will then be replaced by a new allocation. The new allocation is computed by the servers and it can be placed on either the same, or a different node.

I will raise an issue against the Nomad repository to come up with a common sentence to describe this so we can update those two locations.

Thanks,  
jrasell and the Nomad team

---

<div class="post-metadata">

**Author:** ![c.k](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/c.k/32/16109_2.png) [@c.k](https://discuss.hashicorp.com/u/c.k)\
**Post date:** [February 2, 2022, 1:39pm UTC](https://discuss.hashicorp.com/t/api-alloc-stop-doesnt-stop-per-documentation/35123/3 "2022-02-02T13:39:44Z")

</div>

Thank you @jrasell for the quick reply. I appreciate your assistance!