> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/engineering-reference/db/tables/jonaschorum_outboundqueue.md).

# jonaschorum\_OutboundQueue

{% hint style="info" %}
Generated from the staging database schema, with descriptions drafted by agents ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/db/tables/jonaschorum_OutboundQueue.md).
{% endhint %}

## Description

One Snapfix room status change waiting to be sent to Jonas Chorum.

<details>

<summary><strong>Table Definition</strong></summary>

```sql
CREATE TABLE `jonaschorum_OutboundQueue` (
  `id` int NOT NULL AUTO_INCREMENT,
  `uuid` varchar(255) CHARACTER SET latin1 COLLATE latin1_swedish_ci DEFAULT NULL,
  `uuid_tBuilding` varchar(255) CHARACTER SET latin1 COLLATE latin1_swedish_ci DEFAULT NULL,
  `chorum_roomNumber` varchar(50) CHARACTER SET latin1 COLLATE latin1_swedish_ci DEFAULT NULL COMMENT 'Room number to update in Chorum',
  `chorum_cleanStatus` varchar(50) CHARACTER SET latin1 COLLATE latin1_swedish_ci DEFAULT NULL COMMENT 'target: Clean | Dirty | Inspected',
  `chorum_occupancyStatus` varchar(50) DEFAULT NULL COMMENT 'Vacant | Occupied | Out of Order',
  `chorumSynced` tinyint DEFAULT '0' COMMENT '0 = pending, 1 = synced to Chorum',
  `retry_count` smallint DEFAULT '0' COMMENT 'Number of failed sync attempts. Marked deleted at 5.',
  `fDeleted` tinyint DEFAULT '0',
  `fCreatedTs` bigint DEFAULT NULL,
  `fModifiedTs` bigint DEFAULT NULL,
  `fDeletedTs` bigint DEFAULT NULL,
  `fServerTs` bigint DEFAULT NULL,
  `uuid_tUser_CreatedBy` varchar(255) CHARACTER SET latin1 COLLATE latin1_swedish_ci DEFAULT NULL,
  `uuid_tUser_ModifiedBy` varchar(255) CHARACTER SET latin1 COLLATE latin1_swedish_ci DEFAULT NULL,
  `uuid_tUser_DeletedBy` varchar(255) CHARACTER SET latin1 COLLATE latin1_swedish_ci DEFAULT NULL,
  PRIMARY KEY (`id`) USING BTREE,
  UNIQUE KEY `uuid` (`uuid`) USING BTREE,
  KEY `idx_pending` (`chorumSynced`,`fDeleted`) USING BTREE
) ENGINE=InnoDB DEFAULT CHARSET=latin1 ROW_FORMAT=DYNAMIC
```

</details>

## Columns

| Name                    | Type         | Default | Nullable | Extra Definition | Comment                                                                                           |
| ----------------------- | ------------ | ------- | -------- | ---------------- | ------------------------------------------------------------------------------------------------- |
| id                      | int          |         | false    | auto\_increment  |                                                                                                   |
| uuid                    | varchar(255) |         | true     |                  |                                                                                                   |
| uuid\_tBuilding         | varchar(255) |         | true     |                  |                                                                                                   |
| chorum\_roomNumber      | varchar(50)  |         | true     |                  | Room number to update in Chorum                                                                   |
| chorum\_cleanStatus     | varchar(50)  |         | true     |                  | Chorum status name to send, taken from the mapped main status, or Dirty when no mapping is found. |
| chorum\_occupancyStatus | varchar(50)  |         | true     |                  | Always NULL; the queue code never sets it.                                                        |
| chorumSynced            | tinyint      | 0       | true     |                  | 0 = waiting, 1 = sent; a failed send stays 0 and is tried again on every run.                     |
| retry\_count            | smallint     | 0       | true     |                  | No code writes it; the database comment says rows are marked deleted at 5.                        |
| fDeleted                | tinyint      | 0       | true     |                  |                                                                                                   |
| fCreatedTs              | bigint       |         | true     |                  |                                                                                                   |
| fModifiedTs             | bigint       |         | true     |                  |                                                                                                   |
| fDeletedTs              | bigint       |         | true     |                  |                                                                                                   |
| fServerTs               | bigint       |         | true     |                  |                                                                                                   |
| uuid\_tUser\_CreatedBy  | varchar(255) |         | true     |                  |                                                                                                   |
| uuid\_tUser\_ModifiedBy | varchar(255) |         | true     |                  |                                                                                                   |
| uuid\_tUser\_DeletedBy  | varchar(255) |         | true     |                  |                                                                                                   |

## Viewpoints

| Name                                                                                     | Definition                                                                                                                                                               |
| ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [integrations](https://docs.snapfix.com/engineering-reference/db/tables/viewpoint-14.md) | Property management system (PMS) integrations (mappings, room statuses, inbound and outbound queues, webhooks), Deputy, and the keys of the Open API and the vendor API. |

## Constraints

| Name    | Type        | Definition             |
| ------- | ----------- | ---------------------- |
| PRIMARY | PRIMARY KEY | PRIMARY KEY (id)       |
| uuid    | UNIQUE      | UNIQUE KEY uuid (uuid) |

## Indexes

| Name         | Definition                                            |
| ------------ | ----------------------------------------------------- |
| idx\_pending | KEY idx\_pending (chorumSynced, fDeleted) USING BTREE |
| PRIMARY      | PRIMARY KEY (id) USING BTREE                          |
| uuid         | UNIQUE KEY uuid (uuid) USING BTREE                    |

## Relations

```mermaid
erDiagram


"jonaschorum_OutboundQueue" {
  int id PK
}
```

***

> Generated by [tbls](https://github.com/k1LoW/tbls)


---

# 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.snapfix.com/engineering-reference/db/tables/jonaschorum_outboundqueue.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.
