...

• 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.
  • 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 unreachable Subagent is still running the job. Before using the Reset operation users should verify that the Subagent is not running.
• Jobs that must exclude the risk of double job execution 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.

Resources

• JS7 - FAQ - How does JobScheduler terminate Jobs
• JS7 - Agent Command Line Operation
• JS7 - Agent Watchdog

...