> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-smart-connect/setup-and-configuration/queues-and-message-handling.md).

# Queues and message handling

Configure queues to manage message flow and data routing in Smart Connect.

Queues are the central message routing mechanism in Smart Connect. They receive data from connectors, route it through processors, and handle responses. This page covers queue creation, configuration, payload management, and both Core and DMS queue handling.

## What is a queue?

A queue is a temporary storage and routing point for messages in Smart Connect. Each message in a queue:

* Arrives from a connector or external system
* Waits to be processed by a processor
* Is transformed according to business logic
* Is sent to a target system or stored in the queue for later retrieval

Queues decouple data ingestion from processing, allowing asynchronous workflows and retry logic.

## Creating and configuring a queue

Queues are configured through the Smart Connect queue form.

Navigate to **Smart Connect > Inquiries and Reports > Queue** or search for "NANQueueTable" in the F\&O search.

### Basic queue setup

| Field                    | Description                                   | Required | Default |
| ------------------------ | --------------------------------------------- | -------- | ------- |
| Queue name               | Unique identifier                             | Yes      | –       |
| Description              | Purpose and usage                             | No       | –       |
| Connector                | Which connector receives data into this queue | Yes      | –       |
| Processor                | Which processor transforms the queue data     | Yes      | –       |
| Active                   | Enable/disable the queue                      | Yes      | Yes     |
| Priority                 | Processing priority (1-10, higher = sooner)   | No       | 5       |
| Max retries              | Number of retry attempts on failure           | No       | 3       |
| Retry interval (minutes) | Time between retries                          | No       | 5       |

### Queue behavior

1. **Message arrival:** Connector sends data to the queue
2. **Storage:** Message is stored in the queue table
3. **Processing:** Processor reads the queue in priority order
4. **Transformation:** Business logic is applied
5. **Output:** Result is sent to target system or stored for retrieval
6. **Logging:** Outcome is recorded in the queue log

## Payload management

Smart Connect supports two payload handling modes for queues. Choose based on your data size and performance needs.

### Full payload mode

**Configuration:** Store payload data in queue tables

**When to use:**

* Payload size < 500 KB
* Need to reference payload data in the UI without additional lookups
* Troubleshooting requires immediate access to message content

**Performance:** Slower queries on large queues; database storage grows with data volume

**Table:** NANQueuePayloadTable

### Payload-less mode (DMS)

**Configuration:** Store only message ID and metadata; payload stored externally

**When to use:**

* Payload size > 500 KB
* High-volume queues (thousands of messages per day)
* Performance is critical

**Performance:** Faster queue processing; external storage handles large payloads

**Table:** NANQueueTable (payload reference only)

**Document Warehouse integration:** DMS uses payload-less mode for large documents; payloads are referenced from Document Warehouse storage.

## Response logging and status tracking

Message processing results are logged in the Smart Connect queue response log. Search for "NANQueueResponseLogTable" or access through queue monitoring forms to review message outcomes.

### Response log fields

| Field         | Description                                                      |
| ------------- | ---------------------------------------------------------------- |
| Queue name    | Which queue processed this message                               |
| Message ID    | Unique identifier for the message                                |
| Status        | Processing result: Pending, Processing, Completed, Failed, Retry |
| Input data    | Original message from connector                                  |
| Output data   | Transformed message sent to target system                        |
| Timestamp     | When processing occurred                                         |
| Error message | Details if status is Failed                                      |
| Retry count   | Number of retry attempts                                         |

### Monitoring queue health

1. Go to **Smart Connect > Inquiries and Reports > Queue** to view queue status
2. Review metrics:
   * Messages processed (today, this week)
   * Failed messages (count, %)
   * Average processing time
   * Queue backlog (pending messages)

{% hint style="warning" %}
A large backlog or high failure rate indicates the processor may be overwhelmed or there's a configuration issue. Check processor logs and adjust priority or batch size settings.
{% endhint %}

## DMS queue handlers

DMS adds specialized queue handlers for document processing. These route documents to **Birds Document Warehouse** for parsing and validation.

All Smart Connect handlers follow the **Microsoft Dynamics 365 Finance & Operations standard framework** for electronic reporting and data management, ensuring compatibility with F\&O's native capabilities.

### UBL queue handler

* **Purpose:** Process electronic invoices in UBL format
* **Input:** XML-formatted UBL invoice document
* **Processing:** Validates schema, extracts structured data
* **Output:** Structured invoice data + Document Warehouse reference
* **Configuration:** Select processor with UBL template

### Raptor queue handler

* **Purpose:** Process accounting documents
* **Input:** Accounting document (PDF, XML, or JSON)
* **Processing:** Extracts line items, GL accounts, cost centers
* **Output:** Accounting entries ready for F\&O import
* **Configuration:** Select processor with Raptor mapping

### Tungsten queue handler

* **Purpose:** Process purchase documents (PO, goods receipt)
* **Input:** Purchase document format
* **Processing:** Extracts PO lines, quantities, unit prices
* **Output:** Purchase data + Document Warehouse receipt image
* **Configuration:** Select processor with purchase template

## Queue troubleshooting

| Issue                   | Symptom                               | Solution                                                                                                    |
| ----------------------- | ------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| Messages stuck in queue | Status remains "Pending" for > 1 hour | Check if processor is active; verify connector is delivering data; review processor logs                    |
| High failure rate       | Many messages show "Failed" status    | Review error messages in response log; check processor configuration; verify target system is accessible    |
| Slow processing         | Messages take > 5 minutes to process  | Reduce queue priority or batch size; check processor complexity; monitor system performance                 |
| Payload errors (DMS)    | "Payload not found" errors            | Verify Document Warehouse is available; confirm payload reference is correct; check Document Warehouse logs |

## Related pages

* [Connectors and connectivity](https://docs.dynalogic.com/birds-smart-connect/setup-and-configuration/connectors-and-connectivity.md)
* [Processors and transformations](https://docs.dynalogic.com/birds-smart-connect/readme/processors-and-transformations.md)
* [Document processing and formats](https://docs.dynalogic.com/birds-smart-connect/setup-and-configuration/document-processing-and-formats.md) (DMS)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dynalogic.com/birds-smart-connect/setup-and-configuration/queues-and-message-handling.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
