# Published site page shows an export note where a markdown document should be **What you are seeing** A published site page shows an export note where a markdown document should be. --- ## Why it happens The exporter could not resolve the body from any of URL, attachment, stored custom content or the CQL fallback. Usually a build-time URL fetch failure with no stored copy behind it. --- ## What to do Give the macro a page-stored or attachment copy as well as the URL, or fix the source URL. --- ## Settings involved | **Setting** | **Where** | **What it does** | | ---------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Space settings → Space Capability Settin | \- | Auto shows the byline entry only when the page already carries markdown; Always pins it in every page's byline in that space; Never hides it there. Stored on the space property \_capable under capabilities.alway | --- ## Limits that apply here | **Limit** | **Value** | **What happens** | | --------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Large-document scroll mode | 500,000 characters | Past this the document macro shows '⚠️ Large content detected. Rendering in scrollable mode.' and renders inside a fixed 1200px-high scroll box instead of inline. | | Version history entry limit | 50 | Beyond 50 versions the panel shows 'Limited to the last 50 entries'. | --- ## Related [Exported Word or PDF shows raw markdown source in a code blockThe markdown source in a fenced code block, never rendered prose.](https://help.gocapable.com/markdown/exported-word-or-pdf-shows-raw-markdown-source-in-a-code-block.html) [Published Capable Site page looks different from the Confluence pageRaw HTML is off there too, and diagram fences come out as styled code blocks rather than d](https://help.gocapable.com/markdown/published-capable-site-page-looks-different-from-the-confluence-page.html) [Export and published sitesThe rest of this family.](https://help.gocapable.com/markdown/export-and-published-sites.html) --- _Found it? Good._