[cvxluo]

For idempotency in the inbox, for each inbox event, we need something stable to be able to deduplicate events. For issues, it will be the activity id (for comments / assignments), and for investigations, it will be the seer_run_id and generation_id.

[sentry]

Sentry Snapshot Testing

Name	Added	Removed	Changed	Renamed	Unchanged	Skipped	Status
sentry-frontend sentry-frontend	0	0	0	0	808	0	✅ Unchanged

⚙️ sentry-frontend Snapshot Settings

[github-actions]

Backend Test Failures

Failures on 439f460 in this run:

tests/sentry/inbox/test_types.py::InboxEventRetentionTest::test_new_events_are_cleaned_on_the_next_sweep_with_ui_disabled — log

[gw3] linux -- Python 3.13.18 /home/runner/work/sentry/sentry/.venv/bin/python3
tests/sentry/inbox/test_types.py:252: in test_new_events_are_cleaned_on_the_next_sweep_with_ui_disabled
    ISSUE_USER_MENTIONED.record(
E   TypeError: InboxEventType.record() missing 1 required keyword-only argument: 'idempotency_key'

tests/sentry/inbox/test_types.py::RecordTest::test_rollback_does_not_count_recorded_events — log

[gw3] linux -- Python 3.13.18 /home/runner/work/sentry/sentry/.venv/bin/python3
tests/sentry/inbox/test_types.py:471: in test_rollback_does_not_count_recorded_events
    with transaction.atomic(using=router.db_for_write(InboxItem)):
         ^^^^^^^^^^^
E   NameError: name 'transaction' is not defined

[github-actions]

This PR has a migration; here is the generated SQL for src/sentry/notifications/migrations/0018_inbox_event_idempotency.py

for 0018_inbox_event_idempotency in notifications

--
-- Add field idempotency_key to inboxitemevent
--
ALTER TABLE "notifications_inboxitemevent" ADD COLUMN "idempotency_key" varchar(64) NULL;
--
-- Create constraint inboxevent_item_idempotency_uniq on model inboxitemevent
--
CREATE UNIQUE INDEX CONCURRENTLY "inboxevent_item_idempotency_uniq" ON "notifications_inboxitemevent" ("inbox_item_id", "type", "idempotency_key") WHERE "idempotency_key" IS NOT NULL;