We configured a self-hosted diagram renderer but markdown diagrams still go through Capable
What you are seeing
You set up a self-hosted diagram renderer, but diagrams in your markdown are still drawn by Capable.
#Why it happens
Self-hosted rendering for markdown diagrams is switched off at the moment, so Capable draws them whatever you have saved.
#What to do
Treat self-hosted rendering as unavailable for markdown diagrams for now, whatever the saved Diagrams setting says.
#Settings involved
Setting | Where | What it does |
|---|---|---|
Global settings → Permissions | - | Controls who can edit the global asset store, which decides who may create global markdown templates. Diagrams, images, calendar and search share the same permission. |
#Limits that apply here
Limit | Value | What happens |
|---|---|---|
AI diagram repairs per generation | 3 | Only the first three diagram blocks in a generated document are checked and repaired. Any after that, and any diagram language outside the seven that can be repaired, are left exactly as generated. |
New macro retry window | About 2.5 minutes | If a new Markdown macro's content has not appeared yet, it checks again every 15 seconds, up to 10 times, before giving up. |
#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.
