Enqueue Django signal receiver tasks inside the same database transaction with Celery.
npx skills add https://github.com/dvf/opinionated-django --skill dj-signals
Please help me install this Agent Skill. Skill: dj-signals Source: https://github.com/dvf/opinionated-django/tree/main/skills/dj-signals Command: npx skills add https://github.com/dvf/opinionated-django --skill dj-signals
Standard Django signals are synchronous and unreliable: receiver failures propagate errors to the sender, there is no delivery guarantee if the process crashes after a database commit, and there is no built-in retry mechanism for failed side-effect tasks like notifications or cache invalidation.
Use the dj-signals skill to add a reliable async signal for new user registration emails in your Django project, ensuring the email task is only queued after the user account is successfully saved to the database.
High-intent search queries and answers about installing and using this skill.
To ensure Django signals run post-commit, you can use the reliable signals pattern with Celery to enqueue receiver tasks inside the same database transaction. This guarantees tasks are queued only on successful commit and roll back if the transaction fails.
Standard Django signals fail because they are synchronous, causing receiver failures to propagate errors to the sender. They lack delivery guarantees if the process crashes after a database commit and have no built-in retry mechanism for failed side-effect tasks.
To prevent duplicate side-effects from Celery retries, you must design idempotent receivers that safely handle at-least-once delivery. This ensures repeated task execution does not trigger duplicate notifications or other side-effect operations.
The best way to pass data to async Django signal receivers is using JSON-serializable identifiers passed via repositories. This restricts receiver data access to serialized IDs instead of direct ORM imports, ensuring safe async execution.
Synchronous Django signals limit post-commit work by lacking delivery guarantees upon process crashes and having no retry mechanism. Receiver failures also propagate errors directly to the sender, disrupting the core business operation.
CodeAtCodeConfigure Django Celery with Redis broker and django-celery-beat schedules.
duc01226Implement entity event handlers triggering side effects after CRUD operations.
dvfConfigure pytest testing patterns for layered op-django projects.
adelabdelgawadSchedule background tasks with APScheduler and Celery in FastAPI.
