Troubleshooting Index

Scan the Symptom column for the sentence closest to what you would say out loud, then follow the link in the third column. Every row points at the page that owns the fix — this page names the problem, it does not solve it.

Before you scan anything, know this: the single most common report in Leed is not a fault at all. The change was saved, and it has not been published yet. Every edit you make in the CMS is staged until a deployment carries it to your site, so “my change isn’t showing” is nearly always a publish that has not happened rather than something broken. Saved is not live is the model, and Publishing Changes is where you clear it.

Start here: not live, or not working?

Two questions settle most reports before you reach a table.

Question one: did you publish? Every CMS edit — a page, a menu, a page type, a settings field — is staged. An amber dot beside the thing you changed and a row in the Deploy tab’s Your edits card are the whole model: the dot means staged, not broken. Publish, and watch the deployment finish.

Question two: which site are you looking at? Preview and live are two separate builds from two separate branches. A change published from the CMS lands on the preview host; it reaches your live domain only when someone pushes it live. If you are looking at the wrong host, Preview Site vs Live Site explains which change lands where.

flowchart TD
    A["My change isn't visible"] --> B{"Amber dot, or a row<br/>in Deploy → Your edits?"}
    B -- "Yes" --> C["Publish it"]
    B -- "No" --> D{"Did the last<br/>deployment succeed?"}
    C --> D
    D -- "No" --> E["Read the error block on the row"]
    E --> F["When a Deployment Fails"]
    D -- "Yes" --> G{"Preview host,<br/>or your live domain?"}
    G -- "Preview only" --> H["Push live from Deploy"]
    G -- "Live, and still missing" --> I{"Is the page in the menu,<br/>and is the menu published?"}
    I -- "No" --> J["Add it and publish the menu"]
    I -- "Yes" --> K["Real fault — use the tables below"]

A failure with a red error block on the deployment row is decoded at When a Deployment Fails. The exact wording of whatever you were shown is cataloged at Common Error Messages. Things that are known not to work are listed, without hedging, at Known Limitations.

Writing and editing

Pages, URLs and navigation

Documentation sites, themes and tabs

This is the group with the worst signal-to-noise ratio in the product, because almost every one of these fails silently. If a documentation setting appears to have done nothing, it almost certainly failed rather than being ignored, and the row you want is here.

A documentation setting that appears to have done nothing has almost certainly failed silently — Documentation Configuration Reference names each key’s failure mode, and Custom Documentation Themes covers the theme and code-theme cases.

Publishing and deployments

Assets and media

Analytics and Engage

Forms, contacts and email

AI, MCP and the CLI

Each of these is a pointer only — MCP Troubleshooting and CLI Troubleshooting and Exit Codes own the diagnosis.

When it is not a fault

A settings card you cannot see is a role decision. The Settings grid is assembled from the cards your role is allowed to read, so two administrators and one writer genuinely see grids of different sizes. Nothing is hidden by accident — Who Can See What reads the permission model from the role’s point of view.

A search endpoint answering 404 on a Free workspace is the design, not an outage. AI-powered documentation search is a Starter feature, and a public endpoint must never show a visitor a payment error, so it answers as though the route does not exist and the site falls back to its static search index.

A menu item that disappeared right after you published is pointing at an unpublished page. The build drops the whole list item rather than rendering a dead link, so the fix is to publish the target, not to re-save the menu.

If the problem is that a word in an error message means nothing to you, every Leed term has a one-line entry in the Glossary. If you are not yet sure what Leed is, rather than what has gone wrong with it, start at What Is Leed; and if you arrived lost rather than broken, Choose Your Path routes you by what you are trying to do.