> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/nola/canvas/troubleshooting-canvases.md).

# Troubleshooting a Canvas

What happens when a Canvas hits an error, and how to recover

A Canvas is designed to fail gracefully and recover easily. If something goes wrong, it stays contained to the page in question, and Nola can usually fix it for you.

## Errors stay contained

Each Canvas runs independently. If one Canvas runs into a problem:

* **Only that page is affected.** The rest of your app — its navigation, other pages, and standard no-code pages — keeps working normally.
* The Canvas shows a **clear, contained error state** instead of a broken or blank screen.
* You get plain-language messaging, not raw technical output.

This isolation means a single misbehaving Canvas can never take down your whole app.

## Letting Nola fix it

When a Canvas hits an error, Nola can inspect what went wrong and repair it.

1. Ask Nola to fix the page, or use the fix option shown with the error.
2. While she works, the Canvas shows a **"fixing" indicator** rather than the error state, so you know a repair is underway.
3. Nola applies the fix and the page re-renders.

{% hint style="success" %}
**Fixes are free.** If a Canvas generates successfully but then fails to render correctly, asking Nola to fix it doesn't cost you any [credits](https://guides.noloco.io/nola/credits-and-usage.md) — you're never charged twice for one working result.
{% endhint %}

<figure><img src="https://319575345-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifpIQWu0HCVYAt51oT%2Fuploads%2Fgit-blob-66ba0728b135c87a5ef12aff37b60a48ef62208c%2FNola-Error-Fix.png?alt=media" alt=""><figcaption></figcaption></figure>

## Restoring a previous version

If you want to roll a Canvas back to how it was before a set of changes, you can use your app's version history.

A Canvas is included in [app version history](https://guides.noloco.io/settings/publishing/app-version-history.md). When you restore a previous version of your app, its Canvases are restored along with everything else — so you can recover a Canvas's earlier state the same way you'd recover any other part of your app.

{% hint style="info" %}
Restoring a version brings back your Canvases exactly as they were at that point, including their content and configuration.
{% endhint %}

## If a Canvas won't publish

Noloco checks each Canvas before it goes live so a page that can't render correctly doesn't reach your users. If a Canvas is blocking [publishing](https://guides.noloco.io/settings/publishing.md), Nola will flag it with a clear explanation and help you resolve it — usually by fixing the page — so you can publish with confidence.

## Getting more help

If you're stuck, you can always:

* **Ask Nola directly** — describe what you're seeing and she'll try to resolve it
* **Use the in-app support chat** for help from the Noloco team
* Review the [Nola FAQ](https://guides.noloco.io/nola/nola-faq.md) for common questions


---

# 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://guides.noloco.io/nola/canvas/troubleshooting-canvases.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.
