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.
The LiteDB database file becomes corrupt, making the Robot unable to perform read and write operations on the file.
Removing the corrupt LiteDB database file re-enables the Robot to read and write logs.
It is recommended to create a backup of the database file before removing it.
Updated 8 months ago