---
title: "Monitor data received from Service Bus dead letter queue"
slug: "monitor-data-received-from-service-bus-dead-letter-queue"
tags: ["Connectivity Studio", "CS", "Task"]
updated: 2026-04-14T13:21:30Z
published: 2026-04-14T13:21:30Z
canonical: "docs.staedean.com/monitor-data-received-from-service-bus-dead-letter-queue"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitor data received from Service Bus dead letter queue

You can monitor the data that you receive from an Azure Service Bus dead letter queue.

Use the **Received status** to decide if any troubleshooting action is required.

The possible statuses are:

| Status | Description |
| --- | --- |
| New | The data is received from the Service Bus dead letter queue. Based on the Service Bus search definitions, a message is assigned. |
| In process | The data is now imported into D365 F&SCM by the assigned message. |
| Finished | The data import into D365 F&SCM is finished successfully. |
| Error | The data import into D365 F&SCM is finished with errors. |
| Invalid | The data is received from the Service Bus dead letter queue. But, based on the Service Bus search definitions, no message is assigned. |

### Steps

1. Go to **Connectivity studio** > **Inquiries** > **Service Bus queue** > **Received dead letter data**.
2. By default, only received dead letter data records are shown with status '**Error**' or '**Invalid**'. To show all received dead letter data records, clear the **Show errors** check box.

> [!NOTE]
> Note
> 
> You can use the fields of the **Received dead letter data (BisConSbReceivedDataDeadLetter)** table for further processing in D365 F&SCM. Examples of fields that can be used for further processing are:
> 
> - DeadLetterReason: Contains the reason the message was moved to the dead letter queue.
> - DeadLetterErrorDescription: Contains the detailed error description associated with the dead-lettered message.
> 
> You can add these fields to the source document of messages that [process received dead letter data](/data-management/docs/process-received-dead-letter-data). In the message, you can map these fields as desired.
> 
> In the [Service Bus search definition](/data-management/docs/set-up-service-bus-search-definition), define the messages that are used to process received dead letter data.

## Related

- [Monitor and troubleshoot Service Bus dead letter data](/monitor-and-troubleshoot-service-bus-dead-letter-data.md)
- [Data export to Azure Service Bus queue or topic](/data-export-to-azure-service-bus-queue-or-topic.md)
- [Monitor message history](/monitor-message-history.md)
- [Data import from Azure Service Bus dead letter queue](/data-import-from-azure-service-bus-dead-letter-queue.md)