# Workling/Starling: killing a background work from a controller

**URL:** <https://www.ruby-forum.com/t/workling-starling-killing-a-background-work-from-a-controller/188630>\
**Category:** Rails\
**Created:** [May 15, 2010, 12:16am UTC](https://www.ruby-forum.com/t/workling-starling-killing-a-background-work-from-a-controller/188630 "2010-05-15T00:16:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![PierreW](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/da6949/32.png) [@PierreW](https://www.ruby-forum.com/u/PierreW)\
**Post date:** [May 15, 2010, 12:16am UTC](https://www.ruby-forum.com/t/workling-starling-killing-a-background-work-from-a-controller/188630/1 "2010-05-15T00:16:27Z")

</div>

Hello!

There is something I don’t understand with Workling/Starling: it is  
easy to start a background work from a controller, but is it possible  
to stop this background work from a controller?

Say for example:  
user input -\> controller triggers background work aaa  
another user input -\> controller kills background work aaa

I know that when you call MyWorker.asynch\_my\_method it returns a UID,  
but I don’t understand how to use it to kill it?

Thanks a lot!  
Pierre