# Confluent Cloud Dead Letter Queue — Confluent Documentation 6.0.0

**URL:** <https://forum.confluent.io/t/confluent-cloud-dead-letter-queue-confluent-documentation-6-0-0/189>\
**Category:** Managed Connectors\
**Created:** [17 November 2020 17:43 UTC](https://forum.confluent.io/t/confluent-cloud-dead-letter-queue-confluent-documentation-6-0-0/189 "2020-11-17T17:43:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rmoff](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/rmoff/32/3_2.png) [@rmoff](https://forum.confluent.io/u/rmoff)\
**Post date:** [17 November 2020 17:43 UTC](https://forum.confluent.io/t/confluent-cloud-dead-letter-queue-confluent-documentation-6-0-0/189/1 "2020-11-17T17:43:06Z")

</div>

In Confluent Cloud, the connector does not stop when serde errors occur. Instead, the connector continues processing records and sends the errors to a Dead Letter Queue (DLQ). You can use the record headers in a DLQ topic record to identify and troubleshoot an error when it occurs. Typically, these are configuration errors that can be easily corrected.

Read more at [https://docs.confluent.io/current/cloud/connectors/dead-letter-queue.html](https://docs.confluent.io/current/cloud/connectors/dead-letter-queue.html)

---

<div class="post-metadata">

**Author:** ![rmoff](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/rmoff/32/3_2.png) [@rmoff](https://forum.confluent.io/u/rmoff)\
**Post date:** [9 February 2021 13:29 UTC](https://forum.confluent.io/t/confluent-cloud-dead-letter-queue-confluent-documentation-6-0-0/189/2 "2021-02-09T13:29:15Z")

</div>