Introduction

• Consider the wording: a Controller can be operated as a Standalone Controller instance or as a Controller Cluster. The term Controller instance refers to a standalone instance or to a Controller Cluster member instance.
• The outage of a Controller instance will not necessarily stop the execution of workflows with Agents.
  • However, if a workflow includes jobs that are executed with different Agents then the workflow will not be completed and will be put on hold as switching of Agents during workflow execution is performed by the Controller.
  • Find details from the JS7 - Workflow Execution with Controllers and Agents article.
• Testing by SOS includes performing tests for the scenario when a Controller is not available for 24 hours and the Agent executes any scheduled orders. Once the Controller instance is started again then job execution results are updated to the JOC Cockpit History and become visible with the GUI.
• For information about the behavior in case of outages see JS7 - FAQ - What happens to workflows in case of outage of a Controller?

Controller Cluster

If you operate a Controller Cluster then an automated fail-over takes place should the active Controller instance fail. A fail-over typically occurs within 3-5s. Should the standby Controller instance fail then this does not affect the active Controller instance. Running a JS7 high availability cluster gives you the relaxed option not to have to take immediate action if one instance fails. However, should you intend to immediately make available the failed Controller Cluster member instance then the steps explained below similarly apply to the failed instance.

The below troubleshooting hints are intended for users operating a Standalone Controller, the steps explained are not required for users operating a Controller Cluster.

Troubleshooting

See JS7 - How to troubleshoot the outage of a Controller