---
title: "Known limitations"
canonical: "https://support.appfire.com/space/LM/3578560535/Known%20limitations"
format: markdown
---
Review these known limitations before scheduling a large bulk conversion.

|  |  |  |  |
| --- | --- | --- | --- |
| **Category** | **Limitation** | **Workaround** | **Atlassian Ticket** |
| Restricted pages | Restricted pages are not scanned and cannot be converted. | none | [https://jira.atlassian.com/browse/ECO-822](https://jira.atlassian.com/browse/ECO-822) |
| Scan scope size | A maximum of 10 spaces is supported in migration | none |  |
| Forge Macro Support Only | Currently, the Bulk Converter is only supported on the Forge Cloud version of competitor apps. This does not include macros created with the Connect version.<br>Appfire may evaluate support for Connect-based macros in the future based on customer demand and requirements. | none |  |
| LaTeX Equation Rendering During Immediate Export | If you export the document before the Confluence page has fully loaded, some LaTeX math equations may not render correctly in the exported output. | Wait until the page has completely loaded and all math equations are fully rendered before starting the export.<br>Appfire is working on a fix for this behavior and plans to address it in a future release. |  |
| Concurrent editing | When multiple authors save an article during a conversion, version conflict failures are possible. | none |  |
| Parallel jobs | Confluence rate limits (429) are possible. | Wait for the scan and conversion to complete. |  |