...

A number of workflows and jobs have been started, however, the JOC Cockpit the JS7 - Dashboard view displays zero values for the order history and job historythe JS7 - Order History and JS7 - Task History:

Analysis

Possible root causes include

• You that we are shortly after midnight and in fact no jobs were running since the new day. JOC Cockpit makes use of the time zone that is specified with the user profile to determine the begin of the next day.
• The 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 previously was not connected to JOC Cockpit but is connected later on 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 JOC Cockpit, it does not indicate that jobs were not running as this job execution is performed independently from JOC Cockpit.

...

• The  action menu of the active JOC Cockpit widget offers 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. 

...