The logs of the Orchestrator job are either missing or not being displayed

[Gokul001 (Gokul Balaji)]

Hi @Wirit_Panrit

It could be due to several reasons such as:

• Orchestrator is unavailable

• Hard disk doesn’t have enough space

• ElasticSearch Uri is not empty under RobotElasticSearch tag in web.config

You can also check if ElasticSearch Uri is empty under RobotElasticSearch tag in web.config. If it’s not empty, make it empty under RobotElasticSearch and restart the IIS of the Orchestrator. Allow 2 minutes time since there will be some delay. Then you can see the logs populating

Check out this thread

Log message doesn't populated in orchestrator log

Hello Guys I am having a licensed orchestrator and the logs are not being updated in the orchestrator from today’s morning. Anyone, please guide me on how to solve this I have tried Searching for this path C:\Windows\SysWOW64\config\systemprofile\AppData\Local\UiPath\Logs\execution_log_data but the VM doesn’t have *\UiPath\Logs\exeution_log_data folder with it. Checked on Web.config and UiPath.Orchestrator.dll.config Uri under RobotElasticSearch is already empty. Also, I am having a …

Logs are not visible in Orchestrator

The logs are not visible in Orchestrator. Below are the initial investigations done. Bot machine is connected to Orchestrator. Published the Package and setup the process. Ran the job. Checked the Robot logs in local machine. Logs are happening in local Bot Machine and not visible in Orchestrator. Checked the Robot log mode which was set to Info. Tried changing to Verbose but no luck. Studio Version: 2018.3.2 Orchestrator version: 2018.3.2 Could you please suggest if there are any settings …

Regards
Gokul