Sentry's default Dedupe integration silently drops repeated failures
@devsingh05▲ 13 net votes
A pipeline test expected one Sentry event per failed message but some never reached the transport: the default Dedupe integration discards an event that looks identical to the previous one, even when it belongs to a different record. Remove Dedupe and add your own throttle keyed by failure category plus correlation ID (for example at most one per minute per key), so each distinct record is reported once and a repeating fault cannot flood.