Introduction

JobScheduler The JS7 Controller and Agent will restart jobs in a number of situations:

• restart job after termination with error.
• restart job after Agent restart.
• restart job from different a next Subagent in an Agent Cluster in case that the Subagent running the job becomes unreachable. 

Restart

...

Jobs after Error

If a job terminates with error, this includes that the Agent is available and is a witness to the job's failure.

...

If a job fails then the order is set to the failed state. While waiting for the next try in a Retry Instruction, the order will be set to the waiting state.

Restart

...

Jobs on Restart of same Agent after Crash

If an Agent becomes unreachable while executing a job then this can indicate that

...

If the Agent is restarted after crash then it will restart jobs that were running at the point in time when the Agent crashed.

• This applies to Standalone Agents and to Subagents in an Agent Cluster.
• Jobs that must exclude the risk of double job execution can can be exempted from restart if they are marked not being restartable:
  

  Jira
  server SOS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-2151

   

  Jira
  server SOS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1891

For the time that an Agent is unreachable related orders are set to the blocked state. No operation is available on such orders until the Agent can be reached.

Restart

...

Jobs from next Subagent after Subagent

...

Reset

In an Agent Cluster in case that a Subagent becomes unreachable users find the option operation to confirm loss of the Subagent and to restart jobs from a reset the Subagent. This will cause jobs to be restarted from the next Subagent.

• The Manage Controllers/Agents page offers the Reset operation on individual Subagents. The Director Agent will consider this information and will restart jobs from the next Subagent.
  The option
  • Note: The Reset operation has to be applied to the related, unreachable Subagent, not to the Director Agent.
  • The operation should be handled with care as it can cause double job execution if the
  original
  • unreachable Subagent
  is unreachable but
  • is still running the job. Before using
  this option
  • the Reset operation users should verify that the Subagent is not running.
  • Jobs which are not restartable after a user confirmed loss of the Subagent can be marked as such in the job inventory and will be exempted from restart. This applies to jobs that must exclude the risk of double job execution .Selection of the next Subagent is based on the type of Subagent Cluster, for example fixed-priority or round-robin.can be exempted from restart if they are marked not being restartable:
    

    Jira
    server SOS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-

  ...

  • 2151

     

    Jira
    server SOS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key

  ...

  • JOC-

  ...

  • 1891

  • Selection of the next Subagent is based on the type of Subagent Cluster, for example fixed-priority or round-robin.