Mermaid diagram works in mermaid.js elsewhere but fails or looks different here
What you are seeing
A mermaid diagram works in mermaid.js elsewhere but fails or looks different here.
#Why it happens
Diagrams are rendered server-side by Kroki, not by the browser mermaid library, so syntax that only newer mermaid.js supports can fail. Separately, mermaid C4 blocks are silently rewritten to PlantUML C4 before rendering.
#What to do
Stick to syntax Kroki's pinned version supports, and expect C4 diagrams to look like PlantUML C4 rather than mermaid C4.
#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. |
#Related
We configured a self-hosted diagram renderer but markdown diagrams still go through Capable
The self-hosted renderer path is currently disabled by a hard kill switch.
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
Everything else
The rest of this family.
Found it? Good.
