...

Introduction

• The History Service is used to receive events about the execution of workflows and jobs from any connected Controllers and to add them to the JS7 - History.
• As a result, the execution history and logs of orders and tasks become available. Due to the asynchronous nature of JS7 components products this task is performed by a background service.

...

If the History Service is not active and therefore dies does not release events then these events will remain with the Controller and will fill up its journal. Events include any log output that is created from jobs and workflow instructions. Users should make an assumption about the maximum duration of an outage of the History Service during periods of high job frequency. The Controller's journal will grow as large as allowed within the limits of the file system. Due to the fact that individual log output of jobs is included and that jobs are executed at individual frequencies we cannot give an estimate of the growth rate. However, reserving a few GB disk space for both the Primary and Secondary Controllers' journals is required.

...