Django Signal Receiver Error Fix

In this tutorial, you'll learn about Django Signal Receiver Error Fix. We cover key concepts, practical examples, and best practices.

The Problem

You add a post_save signal to create a profile when a user registers. The signal doesn't fire or fails silently. New users have no profile, and you get no error message.

Quick Fix

Wrong — signal receiver not connected

# signals.py
from django.db.models.signals import post_save
from django.contrib.auth.models import User

def create_profile(sender, instance, created, **kwargs):
    if created:
        Profile.objects.create(user=instance)

post_save.connect(create_profile, sender=User)

Output: Signal never fires because signals.py is never imported by Django.

Correct — app ready connection

# apps.py
from django.apps import AppConfig

class MyappConfig(AppConfig):
    default_auto_field = 'django.db.models.BigAutoField'
    name = 'myapp'

    def ready(self):
        import myapp.signals  # noqa

Output: Signal is connected when the app is ready. Profile is created on user registration.

Using decorator

# signals.py
from django.dispatch import receiver
from django.db.models.signals import post_save
from django.contrib.auth.models import User

@receiver(post_save, sender=User)
def create_profile(sender, instance, created, **kwargs):
    if created:
        Profile.objects.create(user=instance)

Debugging silent failures

import logging
logger = logging.getLogger(__name__)

@receiver(post_save, sender=User)
def create_profile(sender, instance, created, **kwargs):
    try:
        if created:
            Profile.objects.create(user=instance)
    except Exception as e:
        logger.exception(f"Failed to create profile for user {instance.id}: {e}")
        raise  # Re-raise to see the error in development

Disconnecting and reconnecting

# Disconnect
post_save.disconnect(create_profile, sender=User)

# Check if connected
connected = post_save.has_listeners(sender=User)
print(f"Signal connected: {connected}")

Prevention

• Always connect signals via AppConfig.ready() in apps.py.
• Use @receiver decorator for cleaner code.
• Log exceptions inside signal handlers — signals suppress errors by default in newer Django.

Common Mistakes with signal receiver error

1. Forgetting deriving (Show, Eq) on custom data types needed for debugging
2. Placing the wildcard pattern first in case expressions, making all subsequent patterns unreachable
3. Using head and tail instead of pattern matching, causing runtime errors on empty lists

These mistakes appear frequently in real-world DJANGO code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ