> 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/process-node-parts/debug-logging-message.md).

# Debug Logging Message

## Description

The *logging* part allows you to log messages/errors to the session log database.

## Use

The *logging* part is available in process nodes under the *Misc* dropdown menu. You can use the log part to save messages/errors by adding the log part to a node when an error occurs or when you want a message to be logged. Logging does not work when the logging profile is set to "FULLSPEED". It does work when it is set to one of the following profiles: DEBUG, DEBUGVIEW, DEVELOPMENT, or PRODUCTION.

## Editor Fields

| Field Name  | Description/Use                                                                                                                                                                                                                                                                                       | Type/Options             | Optional/Mandatory |
| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------ | ------------------ |
| Type        | <p>- <em>Log</em>: If you select this option the message is saved under the category "Log".<br>- <em>Service</em>: If you select this option the message is saved under the category "Service".</p>                                                                                                   | Log \| Service           | Mandatory          |
| Level       | <p>- <em>Info</em>: If you select this option the message is saved under the category "Info".<br>- <em>Warning</em>: If you select this option the message is saved under the category "Warning".<br>- <em>Error</em>: If you select this option the message is saved under the category "Error".</p> | Info \| Warning \| Error | Mandatory          |
| Description | This is a description of the message/error.                                                                                                                                                                                                                                                           | Text                     | Optional           |
| Parameters  | These are the parameters the system can pass to the message/error to retrieve more information.                                                                                                                                                                                                       | Data Object              | Optional           |

## Example

Download and import the following [example project](/release-9/example-gallery/example-projects-for-parts/log-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/process-node-parts/debug-logging-message.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.