...

• Problem: After successfully completing initial operation of Controller and Agents if due to some weird reason the Controller's journal is deleted/damaged then this may fail the coupling with Agents.
  • The JOC Cockpit will report the Agent status "Shutdown". When hovering the Agent Status with the mouse then the full error message will be displayed, for example 
    • AgentNotDedicated: This Agent has not been created yet.
• Solution: This problem can be resolved by restarting the Controller. At the point in time of Controller restart the JOC Cockpit and Agents have to be up and running. In case the problem to couple Agents persists re-register the Agents the JOC Cockpit using the Agents' "Edit" action menu.
  • Consider that loss of a Controller's journal includes that
    • any scheduling objects such as workflows have to be re-deployed,
    • any orders of the Daily Plan have to be re-submitted,
    • any currently running orders are lost.
  • Use of a Controller cluster will leverage such a situation as the Secondary Controller operates a synchronized copy of the journal and will pick up operations immediately. The failed Primary Controller can be started later on will automatically synchronize with the Secondary Controller's journal.

Further Information

For troubleshooting during ongoing operation see JS7 - How to troubleshoot Agent journals