# Robot Messages

**Robot Messages (Logs)** are messages that Robots send to the Orchestrator as they perform Tasks.

The "Robot Messages" screen contains the "Robot Messages" table.

Each Robot message (Log) is reflected in the "Robot Messages" table as a single row.

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-9b4608a76bedcde3f1d6be36852c8252518a47e0%2Fimage%20(182).png?alt=media" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="53"></th><th width="117"></th><th width="363"></th></tr></thead><tbody><tr><td><strong>No.</strong></td><td><strong>Column</strong></td><td><strong>Column Description</strong></td></tr><tr><td>1.</td><td>Robot</td><td>Displays the name of the Robot.</td></tr><tr><td>2.</td><td>Process</td><td>Displays the Process that the Robot is executing.</td></tr><tr><td>3.</td><td>Process Version</td><td>Displays the version of the Process that the Robot is executing.</td></tr><tr><td>4.</td><td>Task</td><td>Displays the Task that the Robot is performing.</td></tr><tr><td>5.</td><td>Type</td><td><p>Displays the type assigned to the Robot message (Log). Possible values:</p><ul><li>Info — information;</li><li>Critical — critical;</li><li>Error — error;</li><li>Warning — warning;</li><li>Debug — debugging.</li></ul></td></tr><tr><td>6.</td><td>Message</td><td>Displays the Robot message.</td></tr><tr><td>7.</td><td>Fields</td><td>Displays the parameters of requests and responses, which may include data types and identifiers.</td></tr><tr><td>8.</td><td>Created</td><td>Displays the date and time when this Robot message was created.</td></tr></tbody></table>

All columns in the "Robot Messages" table can be configured by the User. The functions for configuring table columns are described [here](https://docs.sherparpa.ru/en/sherpa-rpa/sherpa-orchestrator/rabota-v-sherpa-orchestrator/rabochaya-oblast-orkestratora).

## **Logging in the Orchestrator on the Designer Side**

Logs in the Orchestrator are Logs that Robots send themselves. There are a number of system Logs. System Logs are recorded if an error occurs within the script that has not been handled anywhere, and the script crashes.

Any messages or variable values can be logged. For this, the Designer provides two blocks:

* "Log to Orchestrator";
* "Log".

### **Logging with the "Log to Orchestrator" Block**

In the parameters of the "Log to Orchestrator" block, you need to specify a message (any variable of any type) and its criticality level.

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-00ab1a7ef07cddfae3179aebe243dabface8fda9%2Fimage%20(183).png?alt=media" alt=""><figcaption></figcaption></figure>

When using this block, you can choose the logging level:

* Info — information;
* Critical — critical;
* Error — error;
* Warning — warning;
* Debug — debugging.

You can also send a screenshot to the Orchestrator along with the message by checking the "Screenshot" flag:

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-00ab1a7ef07cddfae3179aebe243dabface8fda9%2Fimage%20(183).png?alt=media" alt=""><figcaption></figcaption></figure>

The message will be displayed on the "Robot Messages" screen.

If a screenshot was attached to the Robot's message, the corresponding icon will appear in the "Screenshot" column. Click on the icon to view the screenshot in its original size:

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-3776d5351c2a8377c977d91189ef5947a9723df8%2F1%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>

### **Logging with the "Log" Block**

Another way to log is to check the "Orchestrator. Log" checkbox in the "Log" block in the Designer:

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-a1ba0d7bd700e23fbffa1e77e91d8819691b89d3%2F2025-04-21_22-41-26.png?alt=media" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="52"></th><th width="477"></th></tr></thead><tbody><tr><td><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXep7D-PaUrHHRCs30i6JkTwyJ_OdUSljfwCkbFOn35v30ktV0mL0pWPWCsMS9PLLaEC2x5ji5JSoKwJlEgrlT0pwb2CBuJACL_aHw8d0ekCUZXnbaWXBuh0tQ3s3k2lbSF7RwppxQ?key=6sbXsIGaTS3XX9nMXq1GDfiN" alt="" data-size="line"></td><td>It is not recommended to use logging to the Orchestrator within the body of loops with a short interval, as this may lead to a large number of unnecessary messages. For security reasons, the Orchestrator may limit the maximum number of messages received from the Robot in a unit of time.</td></tr></tbody></table>


---

# 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.sherparpa.ru/en/sherpa-rpa/sherpa-orchestrator/rabota-v-sherpa-orchestrator/ekrany/soobsheniya-robotov.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.