IntegrityError: duplicate key value violates unique constraint "contentcuration_user_email_key"

Sentry Issue: STUDIO-E92

IntegrityError: duplicate key value violates unique constraint "contentcuration_user_email_key"
DETAIL:  Key (email)=(batarazaseniorhigh@gmail.com) already exists.

  File "django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
  File "newrelic/hooks/database_psycopg2.py", line 51, in execute
    **kwargs)
  File "newrelic/hooks/database_dbapi2.py", line 25, in execute
    *args, **kwargs)
  File "django_prometheus/db/common.py", line 68, in execute
    return super(CursorWrapper, self).execute(*args, **kwargs)

IntegrityError: duplicate key value violates unique constraint "contentcuration_user_email_key"
DETAIL:  Key (email)=(batarazaseniorhigh@gmail.com) already exists.

(24 additional frame(s) were not displayed)
...
  File "django/utils/six.py", line 685, in reraise
    raise value.with_traceback(tb)
  File "django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
  File "newrelic/hooks/database_psycopg2.py", line 51, in execute
    **kwargs)
  File "newrelic/hooks/database_dbapi2.py", line 25, in execute
    *args, **kwargs)
  File "django_prometheus/db/common.py", line 68, in execute
    return super(CursorWrapper, self).execute(*args, **kwargs)

Start with the linked Sentry issue and the database call shown in django/db/backends/utils.py, then trace the project’s user creation or update path for the unique email constraint. Confirm how duplicate emails reach the database and add regression coverage; done means the scenario no longer raises this IntegrityError while email uniqueness remains enforced.