...

A number of workflows and jobs have been started, however, values of zero are displayed in the JS7 - Dashboard view displays zero values for the JS7 - Order History and JS7 - Task History:

...

Possible root causes include:

• that we are the current time is shortly after midnight and in fact no jobs were have been running since the start of the new day. note that the JOC Cockpit makes use of uses the time zone that which is specified with in the user profile to determine the begin of the next day.
• that the JS7 - History Service is not connected to the Controller and does not receive information about JS7 - Order State Transitions and log output.
  • If a Controller was previously was not connected to the JOC Cockpit but is connected later on at a later point in time, then in some situations it is possible that the History Service will not receive information about job executions from a Controller.
  • This problem affects the visibility of job history entries with in the JOC Cockpit , - it does not indicate that jobs were have not been running as job execution is performed independently from of the JOC Cockpit.

Solution

Restart the JS7 - History Service from the JS7 - Dashboard view like this:

...

• The  action menu of the active JOC Cockpit widget offers includes the Restart Service -> History Service operation.
• If the service was previously detached from the Controller then it should start to report history entries within approx. 20s. 

Should a restart of If restarting the History Service does not resolve the issue then check the following log files for the root cause of the problem:

...

Both log files are available from in the ./logs sub-directory of the JOC Cockpit configuration directory , see - see the JS7 - Log Files and Locations article for more information.