# Sherpa Orchestrator: Frequently Asked Questions

**Question:** What to do if there is a memory shortage issue for the script? (example in the screenshot)

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeiMF6oHm2wNrwqbVrIIf4FTM3AA8ve21dFzNy3hlQmpOiHkeCHWmQBwu4Y7HtYfEHcBrz_Zl5agnG1etVn3CA8znwRmY-OeDfoobVnPgTHXNWEHNUyT64LFh59YSmvfk6OCodMQxIAgC6g0lAVmZwhxTQu?key=Yh07uiGO-Z2MN5VIrN16pA" alt=""><figcaption></figcaption></figure>

**Answer:**\
**1. If using the Docker version:** You need to set `memory_limit = 2048M` or higher in `backend\config\php.ini`. Then you need to restart the container.\
**2. If using the Local version:** You need to set `memory_limit = 2048M` or higher in the `php.ini` file (it may be located at different paths depending on the OS used). Then you need to restart nginx.

**Question:** How to connect `phpMyAdmin` (in the Docker version)?

**Answer:**\
1\. Download the archive and copy it to the server in `/opt.`

`https://sherparpa.ru/downloads/private/SherpaRPAOrcDocker/phpmyadmin.tar.gz`

2\. Load the image into Docker.

`cd /opt/SherpaOrchestrator`

`docker load —input phpmyadmin.tar.gz`

`cd /opt/SherpaOrchestrator`

`sudo wget -O phpmyadmin.tar.gz`

`https://sherparpa.ru/downloads/private/SherpaRPAOrcDocker/phpmyadmin.tar.gz`

`docker load —input phpmyadmin.tar.gz`\
3\. Uncomment all lines related to `phpmyadmin` in the “`docker-compose.yml`”.

4\. Restart the containers:

`cd /opt/SherpaOrchestrator`

`sudo ./run.sh`

5\. Access the address <http://your\\_orchestrator\\_address:8081>

6\. For authentication, specify:

server: `orchestrator-db`\
username: `root`

**Question:** How to restart the container?

**Answer:** It is not recommended to restart containers manually using the Docker command.

The correct method for restarting in the Docker version is the `run.sh` script (run from the default installation directory `/opt/SherpaOrchestrator`). That is, you need to navigate to the installation directory in the console (command `cd` folder\_address) and execute the command `sudo ./run.sh` (sometimes `sudo` is not needed).

**Question:** What to do if there are processing speed issues with a large number of simultaneously running robots?

**Answer:** If there are many robots running simultaneously (if there are issues with request speed), then in the config\
`backend/config/php-fpm.conf`\
the parameter `pm` should be set to `static` (in new builds of the Orchestrator, it is set this way by default).\
To make the Orchestrator process many requests (heartbeat) from a large number of simultaneously running Robots faster, the parameter `pm.max_children` can be increased (the default is set to 8).\
When making any changes to the config, the container must be restarted.\
If you have a local installation without Docker, you need to find the path to `php-fpm.conf`, make the changes mentioned above, and restart `php-fpm`.

**Question:** Can you please tell me if it is possible to assign an input parameter in the orchestrator when creating a job or when defining a trigger?

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXewI_kl1UWitjbr8lAhrckU7HlXkcX55a9vPJz0Pt5x1rVgR70Bxr1arUsUe3OZ82Ee85HRw3O6RICtEo_NbvErW0uM8r27Z1paxluY-yK6jfXweYXdR4tDeeSr56QI6plez6VWp_3R5oXBb90H8DA7SzlY?key=Yh07uiGO-Z2MN5VIrN16pA" alt=""><figcaption></figcaption></figure>

**Answer:** In the Orchestrator, create a task in some queue and write the parameters you want to pass into that task. Then in the Orchestrator Trigger on the “Queue” tab, select the item "Assign the default task to created jobs" and choose that task. After that, in the robot script, use the "Get default task" block from the Orchestrator palette to retrieve your parameters.

**Question:** What to do if Robots (or other objects) have disappeared from the Orchestrator?

**Answer:** They may have been accidentally deleted. Most records in the database are deleted via soft delete, meaning that in the `is_deleted` column, it is simply marked as 1, while the record remains in the database. If something is missing, it can be restored manually through the database by finding the necessary object and changing `is_deleted` to 0.

**Question:** How to increase the session time in the web version of the Orchestrator? Now, as I understand, it is 15 minutes by default?

**Answer:** You can raise it to 30 minutes; for this, add the following parameters to the config `backend/config/php.ini`:

`session.gc_maxlifetime = 1800`

`session.cookie_lifetime = 1800`

After that, you need to restart the containers.

You can set larger values (in seconds), but at the script level, there is a session termination implemented after 30 minutes of inactivity. This method is relevant for the Docker version. For the non-Docker version, you need to make changes to the same parameters (but the path to the config will be different and will depend on the OS used). In that case, after making changes, you will need to restart the web server.


---

# 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/sherpa-orchestrator-otvety-na-chasto-zadavaemye-voprosy.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.