UiPath Robot Guide

Duplicate Execution Logs

Observed Behavior

On rare occasions, duplicate log entries would be written to the LiteDB local database, leading to an excessive amount of disk space taken by the log database. As a result, Orchestrator would also receive multiple duplicate log entries. Since the Robot could not write logs inside the database file, repeated attempts were made, without marking each attempt as sent.

Cause

The LiteDB database file becomes corrupt, making the Robot unable to perform read and write operations on the file.

Solution

Removing the corrupt LiteDB database file re-enables the Robot to read and write logs.

Note:

It is recommended to create a backup of the database file before removing it.


Duplicate Execution Logs


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.