# Exception Handling

In complex use cases, typically with a lot of integrations or important services running on a schedule, errors are bound to happen at some point.

The action node Catch Exception may be used for catching exceptions and handling them. In some cases, you may even want to re-throw your own custom exception using Throw Exception action node (and catch them somewhere else).

In this Topic, we refer to the documentation of the Catch Exception action node. We also refer to an article (and Showroom example) of an Event Log design - where an Event logging and monitoring system is created.

**Articles**:

* [Catch Exception](/library/action-nodes/catch-exception.md)
* [Event Log Design](/how-to/logic-and-flow/event-log-design.md)

**Showroom Example**:

* [Event Log Design](https://showroom.appfarm.app/architectural-designs/event-log)


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.appfarm.io/appcademy/appfarm-professional/logic-and-flow/exception-handling.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.