> For the complete documentation index, see [llms.txt](https://docs.heisenware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heisenware.com/app-builder/build-backend/extension-nodes/error-handler.md).
# Error handler
The error handler manages errors thrown by a function. It opens a separate output that only activates when the function fails or throws an exception. Unlike the other extension nodes, the error handler attaches directly to a function only, not to other extension nodes.
Build a dedicated logic path from this output to handle error conditions, for example to log the error details to a database or display an error message in the UI. Wire the error handler to widgets or function triggers like any other output, and chain further extension nodes behind it, for example a modifier to reshape the error message.
The captured error message appears below the error handler. Right-click it to clear the content or delete the node.
Error simulator function with captured error message and JSONata modification
---
# 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://docs.heisenware.com/app-builder/build-backend/extension-nodes/error-handler.md?ask=&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.
.png?alt=media)