BlueConfetti

FLINT MARKDOWN EXPORT · CHECK

Understand export warnings and fix missing or changed content

Find out what a warning means, where it shows up in the files, and what to change before you export again.

Finished result

A runbook page exported with four warnings and one HTML table. For each, you will know the exact message, what ended up in the Markdown and the most likely fix.

Example: a service desk runbook

The fictional Service desk runbook page (4001) has a dashboard screenshot, an escalation matrix with a merged cell, a status board from another app, a Jira issue list and a wiring diagram image. Exported alone in Standard Markdown, the export summary reads Export completed with 4 warnings. Review the details below before using the files.

Where warnings appear

To check one page quickly, click its title in the page list and choose Prepare page preview. That preview prepares the page alone; use the full preview for links between pages and the final ZIP layout.

The four warnings and the table

Warning textWhat the file containsWhat to do
Jira issue list not exported (JQL: project = DESK AND priority = High AND resolution = Unresolved)An HTML comment: <!-- macro: jira jql="…" -->Jira issue lists are not exported in this release. Keep the live list in Confluence, or add the issues the export needs to the page as text or a table.
Macro "status-board" not rendered: could not be renderedA marker: <!-- macro: status-board -->Flint asks Confluence to render macros it does not convert itself. When that fails, the marker remains. Export again later; if it persists, treat the content as a known gap or replace the macro with page content.
queue-dashboard.png could not be downloadedThe image still points to the Confluence attachment: ![Queue dashboard](https://example.atlassian.net/wiki/pages/viewpageattachments.action?pageId=4001&preview=queue-dashboard.png)Check the file opens for you in Confluence, then export again. Until then the image only displays for readers who can open Confluence.
Attachment not found: Desk phone wiringThe image’s alt text as plain text: Desk phone wiringThe page refers to a file that is not among its attachments, for example an image that belongs to another page or was removed. Re-insert or attach the image on this page.
No warningThe escalation matrix is an HTML <table> with rowspan="2"Merged cells and complex cells keep HTML structure. Confirm your destination displays HTML tables; otherwise simplify the table in Confluence.

The rendering message can also end in rendering timed out, no rendered output or render limit reached. Each still leaves a marker in the file.

The page, as exported

## Queue dashboard

![Queue dashboard](https://example.atlassian.net/wiki/pages/viewpageattachments.action?pageId=4001&preview=queue-dashboard.png)

## Escalation matrix

<table><tr><th><p>Severity</p></th><th><p>First response</p></th><th><p>Escalate to</p></th></tr><tr><td rowspan="2"><p>High</p></td>…</table>

## Team status board

<!-- macro: status-board -->

## Open escalations

<!-- macro: jira jql="project = DESK AND priority = High AND resolution = Unresolved" -->

## Wiring diagram

Desk phone wiring

Fix, then export again

  1. Decide which warnings matter for this copy. A runbook binder may need the escalation issues; an archive may accept a marker.
  2. Fix the source in Confluence (restore the image, replace the macro, add the issues), or change the scope if a page should not be in the export.
  3. Export again with the same settings. To confirm which pages changed, load the previous manifest.json under Compare with a previous export; see comparing exports.
  4. Check the new warnings lists before replacing the earlier copy.

Other messages in the summary

Sample files

Sample files on this page are fictional. They were produced by the released Flint Markdown Export exporter, using a simulated Confluence site instead of a live one. Interface labels come from the released app; this guide contains no app screenshots.