Problem

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

Analysis

Possible root causes include

You 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 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 is performed independently from JOC Cockpit.

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

Explanation:

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.

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

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