Filled in 'Markdown description' in the macro config, was warned about unsaved changes, saved, and t
What you are seeing
I filled in 'Markdown description' in the macro config, was warned about unsaved changes, saved, and the description was gone.
#Why it happens
The macro does not save the description you type, even though a document can hold one. The unsaved-changes warning still counts a description edit as a change, so you are asked to save something that is then dropped.
#What to do
Do not rely on the macro's description field. Set a description on the document from the Capable Markdown library page instead.
#Settings involved
Setting | Where | What it does |
|---|---|---|
Global settings → Capabilities → Markdown | - | Hiding Markdown removes it from the Capable nav bar and the content byline menu across the site. It does not stop existing macros from rendering. |
Space settings → Space Capability Settings | - | Auto shows the byline entry only when the page already carries markdown. Always pins it in every page's byline in that space. Never hides it there. |
Global settings → Features → AI integrations | - | 'Allow AI-powered features across Capable. Turn off to disable AI for all users.' Turning it off removes the Studio (Generate markdown with AI) section from the markdown catalogue. |
#Limits that apply here
Limit | Value | What happens |
|---|---|---|
Large-document scroll mode | 500,000 characters | Past this size the document macro shows '⚠️ Large content detected. Rendering in scrollable mode.' and displays the document in a scrolling box instead of inline. |
MCP / Rovo document size cap | 512 KB (524,288 characters) | Creating or updating a markdown document through the Capable tools is refused, not cut short, if it is larger. You are asked to split it. |
#Related
Logged-out reader on a public page sees 'Sign in to view this markdown' instead of the document
The document is loaded from an external URL. URL markdown is fetched through the Capable p
Diagram code blocks show as plain code instead of pictures for some readers
Rendering a fence needs a Capable client token, which logged-out readers do not have. This
Everything else
The rest of this family.
Found it? Good.
