[Solved] Why does AsyncResult.status sometimes return 'PENDING' even if the task was sent to the broker? — Ans: Because the task result backend has not received any update yet | Django

Django - Celery and Background Tasks

Why does AsyncResult.status sometimes return 'PENDING' even if the task was sent to the broker?

ABecause the task result backend has not received any update yet

BBecause the task ID is invalid

CBecause the broker is down

DBecause the task has already finished

Step-by-Step Solution

Solution:

Step 1: Understand status flow in Celery
When a task is sent, the broker queues it, but the result backend may not have updated status yet.
Step 2: Explain why status shows PENDING
Until the backend receives a status update, AsyncResult.status returns 'PENDING' even if the task is queued.
Final Answer:
Because the task result backend has not received any update yet -> Option A
Quick Check:
PENDING means no backend update yet [OK]

Quick Trick: PENDING means no result backend update yet [OK]

Common Mistakes:

MISTAKES

Master "Celery and Background Tasks" in Django

9 interactive learning modes - each teaches the same concept differently

More Django Quizzes

Why does AsyncResult.status sometimes return 'PENDING' even if the task was sent to the broker?