We configured a self-hosted diagram renderer but markdown diagrams still go through Capable
What you are seeing
Configured a self-hosted diagram renderer but markdown diagrams still go through Capable.
#Why it happens
The self-hosted renderer path is currently disabled by a hard kill switch.
#What to do
Treat self-hosted rendering as unavailable for markdown fences today, regardless of the saved Diagrams setting.
#Settings involved
Setting | Where | What it does |
|---|---|---|
Global settings → Permissions | - | Controls edit access to the GLOBAL asset store. Which is what governs who may create Global markdown templates. It is shared with diagrams, images, calendar and search because they all use one Confluence custom content t |
#Limits that apply here
Limit | Value | What happens |
|---|---|---|
AI diagram repairs per generation | 3 | Only the first three fenced diagram blocks in a generated document are validated and repaired; anything beyond that, and any language outside the seven repairable ones, passes through verbatim. |
New-macro retry window | 10 retries at 15 seconds ≈ 2.5 minutes | When an asset should exist but has not indexed yet, a freshly inserted document macro retries the fetch on a 15-second timer up to 10 times before giving up. Legitimately-unconfigured macros do not po |
#Related
Big document renders inside a small scrolling box with a '⚠️ Large content detected' banner
The document is over 500,000 characters, so the macro switches to a fixed 1200px-high scro
Editor is replaced by 'Invalid markdown provided' naming some other language
The renderer threw on the current text AND language detection guessed something other than
Everything else
The rest of this family.
Found it? Good.
