> For the complete documentation index, see [llms.txt](https://help.urbanpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.urbanpiper.com/business-manager/finding-and-fixing-menu-publish-errors.md).

# Finding and Fixing Menu Publish Errors

Learn how to find out why a menu publish failed on a platform and how to fix the errors.

### Step 1: Log in to Atlas

Log in to your **Atlas** portal.

### Step 2: Open the Logs section of a location

Go to **Locations** and click on the location.

![Locations page in Atlas with the Locations menu and a location highlighted](https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Fgit-blob-664128627e993174d2566a989edf85027a1bb19b%2Fatlas-locations-list.png?alt=media)

In the location panel, click on the **Logs** tab.

![Edit location panel with the Logs tab highlighted](https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Fgit-blob-c4989dcc52a447de0350aaad28f80d3c1415a640%2Fatlas-location-logs-tab.png?alt=media)

### Step 3: Check the errors

You will see a **fix errors** option against the respective platforms. Click on it to see the issue or errors.

![Location logs showing a failed menu publish with the fix errors link highlighted](https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Fgit-blob-a0352f3dd0d00a20d6f458011ada494539285714%2Fatlas-location-logs-fix-errors.png?alt=media)

### Step 4: Fix the errors and republish the menu

Fix the errors until all of them are resolved, and then republish the menu to get a success response.

{% hint style="info" %}
**Note:** If the error is not clear or does not show why the publish is failing, reach out to UrbanPiper Support via email at <support@urbanpiper.com> or chat.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.urbanpiper.com/business-manager/finding-and-fixing-menu-publish-errors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
