Identify and Fix Issues in Your Exports

When Scroll Word Exporter finds problems during an export, it lists them in the issue report. This page explains each issue, what it means for your exported document, and how you can fix it.

Find an Issue in the Issue Report

The issue report will cover problems related to page content, images, attachments and links, export templates and placeholders, as well as the export process and application setup. If an export finishes with issues, the export dialog shows a message and a link to the issue report.

To find the explanation for an issue, follow these steps:

1. In the export dialog, select View issue report.

2. Find the issue label in the Issue column. The Origin column shows where the issue occurred, for example the affected page.

3. Find the same label in the issue overview on this page and select it.

If you downloaded the issue report with Download issue report, the TYPE column of the issue-log.csv file shows the issue code. In the issue-report.jsonl file of an error ZIP or debug ZIP file, the issue code is the first type value on each line.

Severity levels

Each issue has one of these severity levels:

• Fatal: The export stopped and no file was created (shown in issue-report.jsonl via error ZIP)

• Error: The export finished, but some content is missing or doesn't look as expected.

• Warning: The export finished. Check the affected content before you use the file.

Issue Overview

The following table lists all issues Scroll Word Exporter can report. Select an issue to jump to its explanation.

Fatal

Error

Warning

Page orientation not applied

Issue code: ORIENTATION_NOT_APPLIED | Severity: Error

What happened: A Scroll Landscape, Scroll Portrait, or Scroll Table Layout macro is set to change the page orientation. However, it's placed where Microsoft Word can't start a new section, for example inside a table cell.

Effect on your export: The page orientation stays the same. The rest of the document is exported as usual.

How to fix it: Edit the page shown in the Origin column and move the macro so it sits directly on the page, outside of tables and other macros.

Maximum list depth exceeded

Issue code: MAX_LIST_DEPTH | Severity: Error

What happened: A list on a page has more levels than the Word template supports. Word templates provide list styles for up to eight levels.

Effect on your export: Deeper list levels can't be formatted correctly. If a list is nested very deeply, the export fails.

How to fix it: Edit the page shown in the Origin column and reduce the list to eight levels or fewer. Consider splitting a long list into several shorter lists or using headings to structure the content.

Table column limit exceeded

Issue code: TABLE_TOO_MANY_COLUMNS | Severity: FATAL

What happened: A table in the export has more than 63 columns. Microsoft Word supports a maximum of 63 columns per table.

Effect on your export: The export stops and no Word document is created. The issue report doesn't show which page contains the table.

How to fix it: Find the table with more than 63 columns and reduce its columns to 63 or fewer. Consider splitting the table into two tables, or attaching the data as a spreadsheet instead.

Orphaned Scroll Table Layout

Issue code: ORPHANED_SCROLL_TABLE_LAYOUT | Severity: Warning

What happened: A page contains a Scroll Table Layout macro, but there's no table directly below it.

Effect on your export: The macro is ignored, so its layout settings aren't applied to any table.

How to fix it: Edit the page shown in the Origin column and move the Scroll Table Layout macro directly above the table it should format. If you don't need the macro, remove it.

Widgets not supported

Issue code: WIDGET_NOT_SUPPORTED | Severity: Error

What happened: A page uses the Widget Connector macro to show content from another website, for example a video or a social media post. This type of content only works in a web browser.

Effect on your export: The widget isn't included in the export. In most cases, its web address is shown instead.

How to fix it: Widgets can't be exported. Consider adding a link or a screenshot of the content to the page, so readers of the export can still find it.

Multimedia macro contains invalid height parameter

Issue code: INVALID_MULTIMEDIA_MACRO_HEIGHT_PARAM | Severity: Warning

What happened: A Multimedia macro has a height value that can't be read, for example 300px or 50 %.

Effect on your export: The default height is used instead.

How to fix it: Edit the macro on the page shown in the Origin column and enter the height as a plain number, for example 300, or as a percentage, for example 50%.

Unknown macro found

Issue code: UNKNOWN_MACRO_IN_CONTENT | Severity: Error

What happened: A page contains a macro that Confluence doesn't recognize, for example because the app that provides it was uninstalled. Confluence shows an unknown macro box in its place.

Effect on your export: The unknown macro box is left out of the export.

How to fix it: Edit the page shown in the Origin column and remove the macro or replace it with a working one. If the macro belongs to an app that was removed, ask your Confluence administrator whether the app should be installed again.

Editor error placeholder found

Issue code: ERROR_PLACEHOLDER_IN_CONTENT | Severity: Error

What happened: A page contains an element that Confluence couldn't display, for example a broken image or macro. Confluence shows an error placeholder instead.

Effect on your export: The error placeholder is left out of the export.

How to fix it: Edit the page shown in the Origin column and correct or remove the broken element.

Translation missing

Issue code: MISSING_TRANSLATION | Severity: Warning

What happened: The page is part of a Scroll Content Manager translation that isn't finished yet. Some content on the page isn't translated.

Effect on your export: The page is exported as it is, including the parts that aren't translated yet.

How to fix it: Finish the translation of the page in Scroll Content Manager, then export it again.

Unsupported content type

Issue code: UNSUPPORTED_CONTENT_TYPE | Severity: Error

What happened: The page tree you export contains a type of content that can't be exported. Pages, blog posts, folders, embeds, databases, and whiteboards are supported.

Effect on your export: The unsupported item and everything below it in the page tree are skipped.

How to fix it: Check the content type named in the Explanation column. Consider moving pages you need in the export so they're no longer below the unsupported item in the page tree.

Missing included content

Issue code: MISSING_INCLUDED_CONTENT | Severity: FATAL

What happened: A page uses an Include Page or Excerpt Include macro, and the included page couldn't be processed.

Effect on your export: The export stops.

How to fix it: Open the page shown in the Origin column and check that the included page still exists and that you can view it. Update or remove the macro, then export again. If the problem continues, contact K15t support and include the error ZIP file.

URL not found

Issue code: URL_RESOURCE_NOT_FOUND | Severity: Error

What happened: An image or other file couldn't be downloaded from the address shown in the Origin column. The address might no longer exist, the website might be too slow to respond, or access to it might be blocked.

Effect on your export: The image or file is missing from the export.

How to fix it: Open the address in your web browser to check that it still works. If it doesn't, update or remove the image or link on the page. If it works in your browser, the export might not be able to reach the website, for example because it's on a private network. In this case, contact your Confluence administrator.

Blocked by allowlist

Issue code: BLOCKED_BY_ALLOWLIST | Severity: Error

What happened: A page shows an image or other file from another website. The Confluence allowlist, which controls which websites Confluence can connect to, doesn't include this website.

Effect on your export: The image or file is missing from the export. The issue report usually also shows URL not found for the same address.

How to fix it: Ask your Confluence administrator to add the website shown in the Origin column to the Confluence allowlist.

Missing external attachment

Issue code: MISSING_EMBEDDED_ATTACHMENT | Severity: Error

What happened: A page shows or links to an attachment that is stored on another page or in another space, and that page or space couldn't be accessed. For example, the space was deleted or you don't have permission to view it.

Effect on your export: The attachment is missing from the export.

How to fix it: Check that the page or space with the attachment named in the Explanation column still exists and that you can view it. If it doesn't exist anymore, upload the attachment to the page you export or update the link. Links to attachments are only included when Embed referenced attachments is turned on in the export settings.

Unknown attachment found

Issue code: UNKNOWN_ATTACHMENT_IN_CONTENT | Severity: Error

What happened: A page refers to an attachment, for example an image, that doesn't exist anymore. Confluence shows a broken attachment placeholder instead.

Effect on your export: The broken attachment placeholder is left out of the export.

How to fix it: Edit the page shown in the Origin column, then upload the missing file again or remove the reference to it.

Unknown placeholder

Issue code: UNKNOWN_PLACEHOLDER | Severity: Warning

What happened: Your Word template contains a placeholder that isn't recognized, for example an outdated Scroll Content Manager placeholder.

Effect on your export: The placeholder is left out of the export.

How to fix it: Open the Word template, find the placeholder named in the Explanation column, and remove or replace it.

Invalid date format

Issue code: INVALID_DATE_FORMAT | Severity: Error

What happened: A date placeholder in your export template uses a date format that can't be read, for example because it contains unsupported letters.

Effect on your export: The date is shown in the standard format yyyy-MM-dd HH:mm:ss instead.

How to fix it: Edit the date placeholder in your export template and enter a valid date format, for example dd.MM.yyyy or MMMM d, yyyy. The format that caused the issue is shown in the Explanation column.

Fallback value for page property unavailable

Issue code: PAGE_PROPERTY_FALLBACK_NOT_AVAILABLE | Severity: Warning

What happened: Your export template uses a page property placeholder. The page property isn't set on the exported page. It also couldn't be found on the root page of the document or on the space homepage, which are used as fallbacks.

Effect on your export: The placeholder is empty.

How to fix it: Add the page property named in the Explanation column to the root page of the document or to the space homepage. Alternatively, set a default text in the placeholder settings, so the export shows that text when the property is missing.

Page property not found

Issue code: PROPERTY_RENDERING_ERROR | Severity: Error

What happened: Your export template uses a page property placeholder. The property isn't set on the exported page, and the property couldn't be loaded from the fallback page either.

Effect on your export: The placeholder is empty or shows its default text.

How to fix it: Check the page property named in the Explanation column on the exported page and on the fallback page shown in the Origin column. Make sure the Page Properties macro is set up correctly and that you can view both pages.

Custom placeholder not resolved

Issue code: INVALID_CUSTOM_PLACEHOLDER | Severity: Error

What happened: Your export template uses a placeholder that another app installed in Confluence provides. That app reported an error while the placeholder was being filled.

Effect on your export: The value is missing from the export or replaced by an error message.

How to fix it: Contact the vendor of the app that provides the placeholder. The placeholder name is shown in the Explanation column.

Custom placeholder failed to execute

Issue code: UNSUPPORTED_CUSTOM_PLACEHOLDER | Severity: Error

What happened: Another app installed in Confluence provides placeholders for export templates. That app reported an error when the export started, so its placeholders couldn't be loaded.

Effect on your export: Placeholders from that app are empty in the export.

How to fix it: Contact the vendor of the app that provides the placeholder. The placeholder is shown in the Explanation column.

Communardo Metadata value could not be loaded

Issue code: COMMUNARDO_METADATA_INTEGRATION_ERROR | Severity: Error

What happened: Your export template uses a placeholder from the Communardo Metadata for Confluence Cloud app, but the metadata couldn't be read from that app. Common reasons are that the app isn't licensed, its export integration is turned off, or you don't have permission to view the metadata.

Effect on your export: The metadata value is missing from the export. In the issue report, this issue might appear without a label or explanation.

How to fix it: Ask your Confluence administrator to check that Communardo Metadata for Confluence Cloud is licensed and that its integration with export apps is turned on. If the problem continues, contact Communardo support.

Table style not found

Issue code: TABLE_STYLE_NOT_FOUND | Severity: Error

What happened: A Scroll Table Layout macro uses a table style that doesn't exist in your Word template.

Effect on your export: The table uses the default table style instead.

How to fix it: Add a table style with exactly the name shown in the Explanation column to your Word template. Alternatively, edit the Scroll Table Layout macro and select a table style that exists in the template.

No fallback paragraph font

Issue code: NO_FALLBACK_TABLE_PARAGRAPH_FONT_STYLE | Severity: Warning

What happened: A table style in your Word template doesn't set its own font, and the template has no Normal paragraph style the table could take its font from.

Effect on your export: Text in tables with this style uses the font Times New Roman.

How to fix it: Open your Word template in Microsoft Word. Set a font in the table style named in the Explanation column, or add a Normal paragraph style to the template.

Word field not up to date

Issue code: FIELD_UPDATE | Severity: Error

What happened: Word documents use fields for content that changes, such as the table of contents, page numbers, and cross-references. These fields couldn't be updated automatically.

Effect on your export: Some fields might show outdated values until you update them.

How to fix it: To update the fields in Microsoft Word, follow these steps:

1. Open the exported Word document.

2. Press Ctrl+A (Cmd+A on macOS) to select the whole document.

3. Press F9 (Fn+F9 on macOS) to update all fields.

4. Save the document.

Could not add print suffixes

Issue code: FAILED_DOCUMENT_LINK_SUFFIX_UPDATE | Severity: Error

What happened: When Optimize export for printing is turned on in the export settings, links to other places in the document get a page reference, for example see page 12. For some links, this page reference couldn't be added.

Effect on your export: The affected links still work, but they don't show a page reference.

How to fix it: Check the links in the exported Word document and add page references manually where needed.

Header/Footer could not be updated correctly

Issue code: HEADER_AND_FOOTER_UPDATE_FAILED | Severity: Error

What happened: When the page orientation changes, headers and footers are adjusted to the new page width. This adjustment failed.

Effect on your export: Headers and footers on some pages might not fit the page orientation.

How to fix it: Check the headers and footers in the exported Word document and adjust them manually. If this happens with every export, contact K15t support and include the error ZIP file.

Placeholder output is blank

Issue code: GENERIC_PLACEHOLDER_ERROR | Severity: Error

What happened: A placeholder in your Word template couldn't be filled, for example because it isn't written correctly or the value it refers to doesn't exist.

Effect on your export: The value is missing from the Word document. The document might show an error text in its place.

How to fix it: Open your Word template and check that the placeholder named in the Origin column is written correctly.

Invalid placeholder output

Issue code: INVALID_PLACEHOLDER_MODEL | Severity: Error

What happened: A placeholder in your Word template produced a value that couldn't be added to the document. The Word template might be damaged.

Effect on your export: The placeholder is empty in the Word document.

How to fix it: Contact K15t support and include the debug ZIP file.

Word template processing failed

Issue code: WORD_TEMPLATE_PROCESSING_ERROR | Severity: FATAL

What happened: The Word file of your export template couldn't be opened or prepared for the export, for example because the file is damaged.

Effect on your export: The export stops and no Word document is created.

How to fix it: Open the Word file of your export template in Microsoft Word to check that it opens correctly. Save it again and replace the file in your export template. If the problem continues, contact K15t support and include the error ZIP file.

Word template document missing

Issue code: WORD_DOCX_FILE_TEMPLATE_MISSING | Severity: FATAL

What happened: The Word file that belongs to your export template couldn't be found when the export started.

Effect on your export: The export stops and no Word document is created. This issue often appears twice in the issue report.

How to fix it: Contact K15t support and include the error ZIP file.

OAuth setup is incomplete

Issue code: OAUTH_SETUP_INCOMPLETE | Severity: Error

What happened: To load images and other files, the app connects back to your Confluence site. The connection settings it needs for this are missing.

Effect on your export: Images or other files might be missing from the export. The issue report often also shows URL not found.

How to fix it: A Confluence administrator can restore the connection settings. To restore them, follow these steps:

1. Go to Confluence Administration > Scroll Word Exporter > Connection Settings.

2. Export the content again.

Opening the Connection Settings page restores the missing settings automatically.

Invalid external conversion JVM arguments

Issue code: EXTERNAL_CONVERSION_INVALID_JVM_FLAGS | Severity: Warning

What happened: Large exports can be converted in a separate process on the Confluence server. A Confluence administrator can set options for this process, such as how much memory it can use. At least one of these options isn't valid or isn't allowed, so all custom options were ignored.

Effect on your export: The export was created with standard settings. Large exports might be slower or run out of memory.

How to fix it: Ask your Confluence administrator to review the JVM arguments for the external conversion. Memory settings such as -Xmx2048m, -XX: options, and logging options are accepted. File paths aren't allowed.

Last updated: October 30, 2026