Celery

Raised as a usability problem by 12 people on Hacker News over 12 years (2014–2025), in 11 threads.

People raised many different problems with Celery, but no single problem has yet been raised by 3 people in 3 different months and threads.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 12 complaints

Badly documented and missing basic features like progress reporting, making it hard to use2025-11-03
Source is tangled and over-engineered, and failures are incredibly hard to debug2024-08-13
Getting it working with Django requires an absurd amount of setup effort2023-05-22
Can't readily decouple Celery task functions from their interfaces in a typesafe way2022-08-23
Official Celery setup tutorial doesn't work, forcing developer to find another guide2022-08-06
Settings renamed by migration tool, unrelated settings changed, new naming doesn't work2021-12-09
Can't find operations documentation explaining RabbitMQ interaction and crash behavior2020-10-06
Documentation shows off complexity instead of the simple way to use it2018-08-08
Confusing overlap between queue and exchange terms makes routing keys and task names hard to understand2017-06-15
Confusing, bad documentation makes configuring tasks hard, causing many debugging evenings2015-07-29
Hides exceptions and fails silently, causing hours of hunting for obscure issues2015-07-29
Shipping UI makes users enter tons of duplicate data2014-02-05