Troubleshooting¶

The most common problems and what to do about them. If your issue isn't here, send feedback from the in-app feedback button.

The render preview is showing an error¶

The Quillmark engine validates frontmatter before producing the PDF. The error message includes a path into the offending field — e.g., /frontmatter/signature_block: required.

Read the path, fix the field, and the preview updates automatically. Common causes:

A required field is empty.
A list field has a scalar value (or vice versa).
An unknown key is set, in a Quill that doesn't accept it. (This is usually a warning, not an error — but some Quills are strict.)

If you can't tell what's wrong, switch to Advanced Mode and look at the raw frontmatter directly.

Office symbols are in the wrong case¶

The renderer uppercases office symbols on the MEMORANDUM FOR line automatically. If you're seeing mixed case in the preview, you may be looking at a field that isn't auto-uppercased — memo_from, references, or the signature block. Hand-uppercase those fields if your template expects all caps.

The Freedom 250 emblem won't go away¶

USAF memos include the Freedom 250 emblem by default. Set freedom250: false in the frontmatter (or untoggle it in the metadata widget) to suppress.

Indorsements won't fit on one page¶

For LOCs in particular, the default 12pt font often spills onto a second page. Drop font_size on the root frontmatter to 11 (or a decimal like 11.5). See Indorsements § Fitting indorsements on one page.

The most common causes:

You were in guest mode and cleared your browser data. Guest documents are saved in browser storage on a single device. Sign in to persist documents server-side.
You're signed in to a different account. GitHub and Google sign-ins are separate identities — a document saved under one isn't visible under the other.
You deleted it. Deletion is immediate and not recoverable through the UI.

The export button is disabled¶

Causes:

The document has a render error. Fix the error (see the preview's diagnostic) and try again.
You've exceeded the per-window export rate limit on this deployment. Wait a few minutes.

I imported a template but it's empty or broken¶

The template's source document may have been deleted or unpublished after you imported. Re-import; if the template is gone, contact the template owner.

Usually a third-party cookie issue. Allow cookies for the TongueToQuill domain (and its OAuth provider — github.com or accounts.google.com) and retry. Private/incognito windows often block these.

The MCP connector isn't responding¶

Verify:

The deployment supports MCP. Not every TongueToQuill instance has the MCP endpoint enabled. Try https://<deployment>/mcp directly — a connected instance accepts MCP-shaped POST requests.
Your MCP client supports Streamable HTTP with JSON responses (not SSE).
Your draft validates. create_document surfaces validation diagnostics as plain text in the response — read the message, fix the field, and retry.

My font looks wrong in the export¶

Letterhead and signature fonts are part of the Quill. They are not user-configurable. If the export font looks off:

Open the rendered PDF in a different viewer. Some browsers' built-in PDF viewers substitute fonts at preview time but embed the right ones at print time.
If the issue persists after downloading the file, it's a Quill bug. Send feedback with the document ID and a screenshot.

"Document exceeds 512 KB"¶

The body limit per document is 512 KB. Most memos are under 10 KB; if you're hitting the cap:

Split the content into multiple documents.
Move large reference material out of the document body and link to it.

My published template is showing the wrong content¶

Templates are snapshots. Edits to the source document don't propagate until you republish from that document. If users are seeing stale content, republish.

Something else¶

Open the in-app feedback panel (Help → Send feedback) with:

What you did.
What happened.
What you expected.
A document ID if applicable.