# Problems with Delayed::Job on Heroku

**URL:** <https://community.rubybench.org/t/problems-with-delayed-job-on-heroku/20>\
**Category:** Uncategorized\
**Created:** [January 8, 2015, 7:00am UTC](https://community.rubybench.org/t/problems-with-delayed-job-on-heroku/20 "2015-01-08T07:00:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/rubybench/original/1X/4ae23b7eff9a1b039e126f05dd734ab09c8ab4b5.png) [@system](https://community.rubybench.org/u/system)\
**Post date:** [January 8, 2015, 7:00am UTC](https://community.rubybench.org/t/problems-with-delayed-job-on-heroku/20/1 "2015-01-08T07:00:58Z")

</div>

We can only deploy to Heroku now when there are no delayed\_jobs running. The reason being that upon deployment, Heroku sends a `SIGTERM` which eventually results in a `SIGKILL` on the job. This creates problems where I have to clean up the docker containers manually and may even leave our data in a dirty state (being cut off when POSTing the results).

We’re current raising an exception whenever we get a `SIGTERM` but that is still bad.

> <https://github.com/collectiveidea/delayed_job/commit/90579c3047099b6a58595d4025ab0f4b7f0aa67a>

Hopefully someone might have a better idea.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/rubybench/original/1X/4ae23b7eff9a1b039e126f05dd734ab09c8ab4b5.png) [@system](https://community.rubybench.org/u/system)\
**Post date:** [January 12, 2015, 2:08am UTC](https://community.rubybench.org/t/problems-with-delayed-job-on-heroku/20/2 "2015-01-12T02:08:14Z")

</div>

Maybe we could also use a queuing system on linux itself. Delayed::Job would just be responsible for pinging the service.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/rubybench/original/1X/4ae23b7eff9a1b039e126f05dd734ab09c8ab4b5.png) [@system](https://community.rubybench.org/u/system)\
**Post date:** [August 4, 2015, 5:57pm UTC](https://community.rubybench.org/t/problems-with-delayed-job-on-heroku/20/3 "2015-08-04T17:57:27Z")

</div>

No longer deployed on heroku.