> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/library/action-nodes/throw-exception.md).

# Throw exception

The Throw Exception action node is used to throw custom exceptions when running an action. [Catch Exception](/library/action-nodes/catch-exception.md) can catch and handle these custom exceptions to facilitate accurate and effective error handling.

### Usage

There are several valuable use cases for the Throw Exception action node:

* **Data validation:** When handling invalid data from form submissions or data received from external endpoints.
* **Improved error messages:** When an error occurs, throwing a custom exception allows you to deliver the user clear and actionable error messages.
* **Improved logging and debugging:** For logging and debugging, throwing a custom exception can provide more specific and detailed information. This is especially useful with an [event log setup](/how-to/logic-and-flow/event-log-design.md).

### Properties

<table><thead><tr><th width="213">Property</th><th>Description</th></tr></thead><tbody><tr><td><strong>Message</strong></td><td>Description of the thrown error.</td></tr><tr><td><strong>Custom Code</strong></td><td>Throw a custom error code to catch this specific error with a Catch Exception action node.</td></tr></tbody></table>


---

# 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.appfarm.io/library/action-nodes/throw-exception.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.