# Dead Letter Queue

**URL:** <https://forum.confluent.io/t/dead-letter-queue/10519>\
**Category:** Kafka Connect\
**Created:** [16 April 2024 14:08 UTC](https://forum.confluent.io/t/dead-letter-queue/10519 "2024-04-16T14:08:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![SangiLearner](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/sangilearner/32/3717_2.png) [@SangiLearner](https://forum.confluent.io/u/SangiLearner)\
**Post date:** [16 April 2024 14:08 UTC](https://forum.confluent.io/t/dead-letter-queue/10519/1 "2024-04-16T14:08:58Z")

</div>

Scenario: I am using Kafka HTTP connector to update addresses in SQL Server db. I have configured it so that after 3 retries, it sends the message to Dead Letter Queue.  
After Address1 landed in Dead Letter Queue, another payload ‘Address2’ updated the same record successfully. So Address1 is now old . There is no timestamp in source or sink to identify if message is stale and should be discarded.  
Question: What mechanism is in place to identify stale messages in dead letter queue when I re-process all messages in dead letter queue in batch at the end of the day ?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/confluentcommunity/original/1X/c49438c90c9df282e9996fdf6971be890c71b65a.svg) [@system](https://forum.confluent.io/u/system)\
**Post date:** [16 May 2024 14:09 UTC](https://forum.confluent.io/t/dead-letter-queue/10519/2 "2024-05-16T14:09:05Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.