I would put celery in that class of software that's good enough to be useful, but enough trouble that you'll never be truly happy with it.

We got a lot of mileage out of it (in a past life) before finally moving our job scheduling to a custom solution built on RQ. Celery caused more than a few headaches -- which is why we ditched it -- but its flexibility probably helped us scale up the service to begin with...