Duplicate Execution Logs

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.

A validation method to ensure the LiteDB file is accessible at all times and not become corrupt was introduced. If the LiteDB file becomes corrupt, the Robot Service needs to be restarted so that a backup is automatically created and a new file is generated to prevent the database from becoming corrupt again.