Logs are not stored in database during the execution of order/task

Current Situation

• For every Task and Order JobScheduler writes log files on the file system as text files.
• The logs are stored in the database once the task is completed and similarly for the order after the order is completed.
• The user is truncating the log files using an external script ( started outside JobScheduler), thus when the task is completed and task log is stored in the database, the content of task logs are lost.

Desired Behavior

• JobScheduler should continuously store the Task and Order logs in to the database, to avoid any loss of logs caused by an external process.

Maintainer Note

• The JobScheduler has a housekeeping process /sos/housekeeping/scheduler_rotate_log for the main log and debug log. The job /sos/housekeeping/scheduler_rotate_log does not truncate or rotate task and order logs.
• Importantly any external process should not rotate or truncate task/order logs since the files exclusively belong to JobScheduler and should not be altered by any external process, while used by the JobScheduler.
• Follow the knowledge base article for the Log Rotation description Log Rotation.
• Article for Debug Log description Debug Log.
• Article for Main Log description Main Log.