Comment 22 for bug 1153077

> Maybe RabbitMQ or Celery have a mechanism for ignoring old jobs. If not, we can add a timestamp check to the job
> implementations themselves.

That's a good point, there is support in Celery for this:
http://celery.github.io/celery/userguide/executing.html#expiration