Celery
v1.13.0 Apache-2.0z4j-celery ยท Upstream project
The industry standard, covered end-to-end.
Celery remote-control actions plus signal and broker-event dual capture. Broker-specific dead-letter replay is deliberately not advertised because a generic retry cannot consume or acknowledge the original DLQ entry.
- Latest
- v1.13.0
- Released
- 2026-10-19
- License
- Apache-2.0
Install
pip install z4j-celery Native actions
-
submit_task -
retry_task -
cancel_task -
bulk_retry -
purge_queue -
restart_worker -
pool_grow / pool_shrink -
add_consumer / cancel_consumer -
rate_limit
Not supported
- requeue_dead_letter (broker-specific DLQ consume/ack and routing required)
- list_dead_letters (no portable dead-letter store)
These are engine-level limitations: the underlying engine does not expose the primitives required to support these actions.
Wiring
How z4j plugs in
Event capture
Signals (in-process) + broker-events monitoring (fanout). Auto-switches based on worker pool type.
Reconciliation
celery.result.AsyncResult, authoritative; covers every backend (redis, rpc, db, etc.).
Paired scheduler
Celery Beat
Native database scheduling for Django and Celery.
z4j-celerybeat
Supports inventory, create, edit, delete, enable, disable and immediate triggering for django-celery-beat PeriodicTasks. Static beat_schedule definitions support inventory and immediate triggering; edit those definitions in application configuration.
Learn moreMore engines