Message Schema

Associated ticket ID

Generic entity ID this message belongs to (for non-ticket entities)

Entity type this message belongs to (e.g. sales_order, purchase_order)

Whether this is an internal note

Type of message

Current message status

For SCHEDULED outbound messages (WP-U6, ADR 0324): the ISO timestamp at which the delayed send job should run. Null/absent for all other messages.

Message direction

Sender email address

Sender mailbox (`email_accounts._id`) for outbound EMAIL messages. Set by composers that offer an account selection; the DRAFT→SENT transition hook sends through exactly this account (and fails visibly when it is unavailable) instead of falling back to an arbitrary tenant mailbox. On send the hook stamps the account that was ACTUALLY used, so older messages / comment-path messages without a selection carry the resolved one. Additive field — sanctioned by the OCTOJA contract note above; absent on old documents.

Recipient email address(es)

CC email address(es)

BCC email address(es)

File attachments referenced by file ID (resolved on send). Inbound EMAIL copies additionally carry `size`/`contentId`/`inline` (ADR 0306): `contentId` maps an inline image's `cid:` reference to its persisted email attachment for render-time resolution.

Message subject

Plain text body

i18n key the client resolves INSTEAD of `body` for system-generated notes. `body` remains the English fallback.

Interpolation values for `bodyI18nKey` (e.g. { ticketNumber: "T-2026-00042" }).

HTML body

AI-generated 2-3 sentence summary of an inbound EMAIL (signatures/quotes stripped). Populated best-effort when AI is active for the tenant; null otherwise. Used as the ticket/activity timeline preview instead of the raw body.

Set by the worker when a lazy on-open summarization ran for an imported message (TANSS migration) — even when the LLM returned nothing (AI off, body too short). Prevents the feed trigger from re-enqueuing the same message on every load. Live-ingested emails do not carry this field.

When the message was sent

Why the last outbound send attempt failed. Written when an async send hook throws; cleared when a later attempt succeeds. Absent on messages that failed before EM-012 — treat as "cause unknown", never as "no error".

How many send attempts this message has had (initial send + resends). Absent on pre-EM-012 documents — read as 1, since reaching SEND_FAILED implies one attempt.

Start of the most recent send attempt, successful or not.

Time-boxed in-flight lock for the resend endpoint, mirroring the inbound conversion lock (ADR 0231): set before the provider call, cleared after it. A stale lock (older than the lock window) is ignored, so a crashed API process cannot strand a message as permanently un-resendable.

When the in-flight lock was taken — basis for the lock expiry.

When the message was received

Email Message-ID from the provider

For inbound EMAIL copies: the `email_messages._id` this message was created from (ADR 0306). The web app uses it together with the attachments' contentId to resolve inline `cid:` images via GET /email-inbox/:id/attachments/:fileId/content.

External message ID for sync deduplication (e.g., TANSS history item ID)

Denormalized display name of the original author, written by the TANSS mirror (ADR 0443). Mirrored rows carry the sync actor as createdBy (never the source author) and many source authors have no Codemeta user at all (ex-employees, system entries) — feeds and the timeline enrichment use a present authorName as-is instead of resolving createdBy. Locally created messages leave it unset and resolve via createdBy.

Origin system marker (e.g. 'TANSS'). Set by the migration import and the live mirror (ADR 0443); together with entity-config externalMaster it makes the message a read-only mirror. Locally created messages carry no source.

External identity for sync dedup, e.g. {system:'tanss', id:'ticketComment:123'} — the subtype prefix keeps comment and mail id sequences disjoint (they collide bare).

In-Reply-To header for threading

References header for threading

Set by composers (e.g. the inbox EmailComposeDialog) that already embed the author's signature into htmlBody client-side, so the DRAFT→SENT transition hook (transition.service.ts sendEmailHook) does not append a second one.

Emoji reactions (Teams-style). Managed exclusively via POST /:resource/:id/reactions — never set directly via create/update (the field is protected). Absent/missing = no reactions.