The job is configured with a timeout setting: if job execution exceeds the timeout then the job will be terminated by the Agent.
Jobs can be terminated using GUI operations and by use of the JS7 - REST Web Service API:
- The Cancel/force operation terminates a running job and fails the order.
- The Suspend/force operation terminates a running job and suspends the order.
- Failed and suspended orders can be resumed.
For restart capabilities of jobs see JS7 - FAQ - Can JobScheduler restart failed Jobs.

Terminating Jobs on Unix

In Unix environments, jobs receive the following signals from the Agent:

...

Crash of the Agent is different to termination:
- The Agent process is forcibly terminated, for example using the OS command kill -9 <agent-pid> on Unix.
- The JS7 - Agent Watchdog will terminate any running job processes. Orders for workflows related to affected jobs will be set to the blocked state.
Crash of the machine or of the container the Agent is operated for will crash the Agent and running jobs. Related orders will be set to the blocked state.
Users have limited control of blocked orders as the Controller does not know the execution status.
- Standalone Agents will restart crashed jobs on restart of the Agent unless jobs are marked being not restartable. No operations on blocked orders can be performed until the Standalone Agent is restarted.
- Cluster Agents allow to confirm loss of a crashed Subagent. In this situation crashed jobs will be restarted from some other Subagent unless they are marked being not restartable. Users control if jobs will be restarted on restart of the crashed Subagent or if they should be restarted from some other Subagent.
- For details about restart capabilities of jobs see JS7 - FAQ - Can JobScheduler restart failed Jobs.

Space shortcuts