Common UiPath Issues and how to solve them

Probelm (Logs are not visible in Orchestrator): 

UiPath Robot's log don't being sent to Orchestrator even though it's availales in executions folder (%localappdata%\UiPath\Logs).

Description:

 The way logs being sent to orchestrator :

• Logs will be sent to execution folder (%localappdata%\UiPath\Logs) always. 
• If Orchestrator is unavailable, logs are stored in a local database (LiteDb) in this path C:\Windows\{SysWOW64 or SysWOW32}\config\systemprofile\AppData\Local\UiPath\Logs\execution_log_data. 
• Sometimes the LiteDb used as cache regardless of connectivity between Orchestrator and Robot
•  Robot's service send logs from LiteDb  to Orchestrator but that sometimes don't happen and cause the issue

Solution:

• Check Orchestrator Database to see if there is available disk space.
•  If the logs file is too big robot fails to delete them from LiteDb  which led Robot to not sending logs to Orchestrator 
•  Sometimes the database file LiteDb get corrupted (Don't know why) which led Robot to not sending logs to Orchestrator (you notice the file is corrupted if file size don't increase) 

 To solve the issue: 

• Delete the folder C:\Windows\{SysWOW64 or SysWOW32}\config\systemprofile\AppData\Local\UiPath\Logs\execution_log_data 
• Restart the service 
• Cache gets cleared and robots start sending logs to Orchestrator

The LiteDb  is encrypted and you can't open it