> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/form-node-parts/error.md).

# Error

## Description

This part allows application users to add an error message to a specific logicnet path. It is a custom version of the comment node but also will cause the tab validation to show an error when the LogicNets engine traverses across the node.

## Use

This is used to show an error message as well as impacting validation icons on tabs of the Assessment Framework. It triggers the validation functionality.

## Editor Fields

| Field Name   | Description/Use                                                                                                                             | Type/Options | Optional/Mandatory |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------ |
| HTML enabled | If you check this checkbox, end-users can format the comment using HTML.                                                                    | Yes \| No    | Optional           |
| Text         | This is the field in which the user enters error text. This section can also contain interpolated text; for example, *$(my\_text\_object)*. | Text         | Mandatory          |
| CSS class    | To adjust the style of the error message enter a class here and add styling to the class in the CSS file.                                   | Text         | Optional           |

## Example

For an example of how to use the validation error part, download and import the Q[\&A Showcase example project](/release-9/example-gallery/how-to-guides/qa-showcase-and-example-project.md) in your workspace.


---

# 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://community-test.logicnets.com/release-9/platform-documentation/form-node-parts/error.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.