[Solved] Why does this signal handler not run when a Profile instance is saved? from django.db.models.... Why does this signal handler not run when a Profile instance is saved? | Django

Django - Signals

Why does this signal handler not run when a Profile instance is saved?

from django.db.models.signals import post_save
from django.dispatch import receiver

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

ASignal is connected to User, not Profile model

BHandler function is missing the sender argument

Cpost_save signal does not work with Profile model

DProfile model does not have a create method

Step-by-Step Solution

Solution:

Step 1: Analyze the signal connection
The handler listens to post_save for the User model only.
Step 2: Reason why it doesn't run on Profile save
Since the signal is not connected to Profile, saving a Profile instance won't trigger this handler.
Final Answer:
Signal is connected to User, not Profile model -> Option A
Quick Check:
Signal sender must match model to trigger handler [OK]

Quick Trick: Signal sender must match model instance saved [OK]

Common Mistakes:

MISTAKES

Assuming handler runs for all models
Confusing handler parameters with sender
Thinking post_save doesn't work with Profile

Master "Signals" in Django

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Perf

More Django Quizzes

Why does this signal handler not run when a Profile instance is saved?

Step 1: Analyze the signal connection

Step 2: Reason why it doesn't run on Profile save

Final Answer:

Quick Check:

Want More Practice?