@JasonHerr You are correct that if the job itself is killing the worker, it would never get processed and would keep killing the workers. 

However, clearing the lock value does not work either. You have no way to know that the worker would ever restart on the host. If you're on heroku the host could be different each time. Same of AWS if you're terminating instances. 

A way of preventing rogue jobs would be to keep an `attempt` columns and only retry a job a maximum of N times. That however adds complexity to QC.