Currently, converting content to the export_view body format is very slow when the content contains a Content Properties Report macro that generates results with Connect macros. For example, the Content Properties Report macro might be pulling data from many Content Properties macros that each contains a static Connect macro.

Ways to get or convert content in the export_view body format include (but is not limited to) the following REST API endpoints:

• POST /wiki/rest/api/contentbody/convert/async/export_view
• GET /wiki/rest/api/content/{id}/history/{version}/macro/id/{macroId}/convert/{to}
• GET /wiki/rest/api/content/{id}/history/{version}/macro/id/{macroId}/convert/async/{to}
• GET /pages/{id}?body-format=export_view

Confluence should improve the performance in this situation, which will consequently improve the performance of apps that rely on export_view.