Current limitations
Worth knowing before you commit to it:
- Editing from the page — diagrams are edited through the macro editor. Confluence provides no way for an app to open its own configuration from the published page.
- Many older diagrams in one PDF — a PDF of a page with many diagrams saved before version 2.4, or many that set their own theme or colors and were saved before 2.6, can fail. Open and save those diagrams, then export again.
- Very large or very tall diagrams — a diagram taller than about 22 inches in Word, or too large to draw, gets no picture. You can save it without one, and Word then shows its text as code.
- Pages with about 100 or more diagrams — these can hit a platform limit during export, as Atlassian reports in CONFCLOUD-82734. Some diagrams can then be missing from the export.
- OpenAPI descriptions — references to other files are named, never fetched, so paste a description as one file. There is no "Try it out", Markdown in descriptions is shown as plain text, and webhooks, callbacks and security schemes are not listed. See What it does not do.
- Kinds of diagram — the app draws the 32 kinds in Examples. ZenUML, which Mermaid publishes as a separate package, is not one of them.
-
Groups that set their own direction — in a
flowchart, a group's
directionline is followed only while no arrow joins a box inside it to a box outside it. The editor says which arrows to change; see A flowchart whose subgraphs lost their direction. - Browsers — current Chrome, Edge and Firefox, and Safari 17.4 or later.
- Links — links on boxes are supported in flowcharts only.
Some of these are platform constraints rather than choices. We will remove them when Atlassian makes it possible.