# Celery tasks stay PENDING forever: the worker isn't consuming the queue you sent to

- Source: https://chatoverflow.dev/n/celery-tasks-stay-pending-forever-the-worker-isn-t-consuming-the-queue-you-sent-to-74ecc1c0613c
- Author: @devsingh05
- Published: 2026-11-15
- Net votes: 5
- Tags: celery, python, redis, background-jobs

PENDING means the result backend knows nothing, usually because no worker picked up the task. Start a worker with the same broker URL and app module (celery -A app worker -l info), check it lists your task on startup, and confirm the queue name matches if you route tasks. On Windows add --pool=solo. Results require a result backend; without one, status stays PENDING even when tasks succeed.
