Snippet

Failsafe Signal Handler with Exception Isolation and Logging

Django signals execute synchronously within the database transaction lifecycle unless explicitly offloaded. Wrapping receiver logic inside exception handling blocks prevents signal failures from aborting the primary database save operation.

snippet.py

python

import logging
from django.db.models.signals import post_save
from django.dispatch import receiver
from django.contrib.auth.models import User
 
logger = logging.getLogger(__name__)
 
@receiver(post_save, sender=User)
def initialize_user_profile(sender, instance, created, **kwargs):
    if not created:
        return
    try:
        # Imagine an external service call or database creation
        logger.info(f"Triggered profile creation sequence for user ID: {instance.pk}")
    except Exception as exc:
        logger.error(f"Failed user initialization signal handler for ID {instance.pk}: {exc}", exc_info=True)

django

Breakdown

@receiver(post_save, sender=User)

Registers the receiver function to respond automatically whenever a User model instance is saved.

if not created:

Ensures heavy execution logic only runs upon new record creation rather than updates.

try:

Isolates the signal payload execution to prevent external downstream failures from bubbling up.

logger.error(f"Failed user initialization signal handler for ID {instance.pk}: {exc}", exc_info=True)

Logs full traceback details without re-raising exception, preserving main process flow.

Previous snippet Next snippet

More Intermediate Python exercises →

Failsafe Signal Handler with Exception Isolation and Logging

Related