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
- The full preview. After Review selection → Prepare full preview, each file with problems shows a Conversion warnings box. Switch to Markdown source to see the exact output.
- The export summary. Expand the warning count under Your export is ready. Pages that could not be read, items that are not pages and files over the size limits are listed separately there.
- manifest.json. Each page has a
warningslist. The top-levelskippedandlimitslists record unread pages, non-page items and size-limit omissions.
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 text | What the file contains | What 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 rendered | A 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 downloaded | The image still points to the Confluence attachment:  | 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 wiring | The image’s alt text as plain text: Desk phone wiring | The 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 warning | The 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

## 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
- Decide which warnings matter for this copy. A runbook binder may need the escalation issues; an archive may accept a marker.
- 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.
- Export again with the same settings. To confirm which pages changed, load the previous
manifest.jsonunder Compare with a previous export; see comparing exports. - Check the new
warningslists before replacing the earlier copy.
Other messages in the summary
- Pages that could not be read are named in the summary and listed under
skippedwith the reasoncould not be read. They are not counted as exported. See checking a snapshot. - Items that are not pages, such as whiteboards and databases, are skipped and listed.
- Files too large to include appear as
… not included: over the 75 MB file limitor the export limit. See images and attachments.
Sample files
- OPS-service-desk-runbook-2026-11-03.zipThe runbook export with all four warnings.
- manifest.jsonThe page entry with its warnings list.
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.