FLINT MARKDOWN EXPORT · HOW-TO
Start a background export and retrieve it later
Let a larger export run on Atlassian infrastructure while you close the window, then come back for the ZIP.
Finished result
A queued job whose ID you saved, a status you can refresh, and a ZIP downloaded before the job expires, one hour after it was created.
When to use it
A browser export prepares everything in the current window and needs your device’s memory for the files and the ZIP. A background export runs in Atlassian-hosted Forge functions as you, using your Confluence permissions, so you can close the window. It does not raise any limit: the 500-page collection cap, 75 MiB per file and 300 MiB of attachments still apply, and each job has a 15-minute execution limit.
Start the job
- Choose the source, pages and output settings as usual.
- In the footer, change Run export from In this window to In background.
- Choose Start background export. The footer shows Queueing background export…, then the Background export view opens.
- Copy the value in Export job ID and keep it somewhere you can find it. It is the only way back to this job.
Prepare full preview always runs in the current window. Preview there first if you need to inspect the output, then start the background job.
Come back to it
- Open Apps → Export to Markdown again and choose History, then Find background export.
- Paste the job ID into Export job ID and choose Refresh status.
- The status is
queued,running,ready,failedorcancelled. While it runs, refresh again; Flint does not send a notification. - When the status is
ready, the view shows the page and warning counts and the expiry time. Choose Download ZIP, then inspectmanifest.jsonfor warnings and omissions.
To stop a queued or running job, choose Cancel export. Cancelling deletes any file the job had started to create.
Expiry, access and failures
| Situation | What you see | What to do |
|---|---|---|
| More than one hour since you started the job | Export job is not available. | Start a new export. Download soon after a job is ready. |
| The job could not finish | Export could not be completed. Check permissions and try a smaller scope. | Check you can read the pages, then retry with fewer pages or attachments. |
| The job ran out of time | Export was interrupted before it completed. Try again with a smaller scope. | Split the export into smaller branches; see batch exports. |
| You lost access to an exported page | The download is refused | Restore access or export again without that page. |
Only the person who started a job can use its ID; administrators cannot open someone else’s job. Before a download, Flint checks again that you can still see each exported page and pages inlined by include macros. Rendered macros can reference additional sources beyond those checks. A ZIP you have already downloaded cannot be revoked; handle it under your organization’s policies.
In your history
A finished background export is recorded in History with the source server-generated. History keeps the details, not the ZIP; after the job expires the archive is gone. See export history.
This guide describes the released background controls and messages. It does not include a recorded job; job IDs and expiry times are specific to each request.