Known Limitations

Diagram Complexity and Size

Large diagrams may render slowly. Diagrams with many nodes and edges (hundreds of elements) can take noticeably longer to render. For complex system maps, consider splitting them across multiple diagrams.
No maximum node count is enforced, but extremely large diagrams may cause browser performance issues or fail to render entirely in memory-constrained environments.

Mermaid version lag. ContentCraft bundles a specific version of the Mermaid library. Syntax features introduced in newer Mermaid releases may not be available until the app is updated.
%%{securityLevel}%% is not supported. The Forge environment manages content security. Custom security level directives are ignored.
HTML in node labels is disabled. For security reasons, Mermaid's htmlLabels option is turned off. Use plain text or basic Mermaid formatting within labels.

Atlassian Cloud only. ContentCraft is a Forge app and is not available for Jira or Confluence Data Center or Server.
Diagrams are not indexed for search. The text content inside Mermaid diagrams (node labels, annotations) is not included in Confluence or Jira search results.
Confluence PDF export. When exporting a Confluence page to PDF, diagram rendering quality depends on the PDF export engine used by your instance and may differ from the on-screen appearance.

Diagrams panel is not available in Jira list view or boards. The Diagrams panel only appears when a Work Item is opened in its full detail view.
Diagrams are not included in Jira issue exports (CSV or bulk exports).

Macro is not available in the legacy editor. The Mermaid Diagram macro requires the new Confluence editor. Pages still using the legacy editor cannot embed ContentCraft macros.
Template previews do not render diagrams. In Confluence template previews, the Mermaid Diagram macro is displayed as a placeholder, not a rendered diagram.