sg_event_id changes on retries — making it useless for deduplication

[linoygabay]

Hey SendGrid team,

Your docs says:

“sg_event_id - a unique ID to this event that you can use for deduplication purposes.”
This implies it's safe to use sg_event_id to detect duplicates.

But this is not true — and it's causing serious issues in production systems.

I’m receiving duplicate webhook events (e.g., from retries or network issues), but each one has a different sg_event_id.
That means:
Same email, event, timestamp, message_id, etc.
But sg_event_id is different every time
So there's no way to tell that these are retries. I’m forced to build messy heuristics just to prevent duplicate processing.

Your documentation explicitly says this field is safe for deduplication.
That’s wrong.

It creates duplicate database entries, inconsistent event logs, and wasted engineering time.
Please either fix the behavior or clearly warn developers about its limitations.

Thanks