High Signals Question 170 of 228

Why prefer transaction.on_commit over doing work directly in post_save?

Python & Django · Speak this in 60–90 seconds · Faridabad & Delhi NCR

PICTURE THIS: HOW TO EXPLAIN IT

IdeaSignals

HowWhat happens inside

Why they askShows real use

Simple meaning

post_save can fire inside an uncommitted transaction that later rolls back, leaving Celery tasks or emails referring to rows that never existed.

WHY — Signals instead of guessing?

Why interviewers care about Signals:

They are checking judgment

on Signals.

A good answer names

the situation, the default choice, and one exception - that reads as experience.

Stay structured

Name the idea, why it exists, then one short example.

Close cleanly

End with when you use it and one common pitfall.

STEPS — What happens step by step?

Before you speak the answer, walk the interviewer through these steps:

1
post_save can fire inside
an uncommitted transaction that later rolls back, leaving Celery tasks or emails referring to rows that never existed.
2
on_commit schedules the function
after a successful commit.
3
Nested atomic() blocks delay
the callback until the outermost commit.
4
Give an example
One tiny concrete case you can say aloud.
5
Common mistake
What juniors usually get wrong.
6
Close
When you pick this over the alternative.

EXAMPLE — See it in action

Here's a short line you can speak, broken into clear beats:

Say this line

“on_commit schedules the function after a successful commit.”

Break into beats

oncommitschedulesthefunctionafter

Speaking order

2987408337471632900

Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.

Key takeaway

post_save can fire inside an uncommitted transaction that later rolls back, leaving Celery tasks or emails referring to rows that never existed. on_commit schedules the function after a successful commit.