...

• The StickySubagent Instruction can be used to execute a number of jobs with the same Subagent of a JS7 - Agent Cluster. Use of Agent Clusters is subject to the terms for clustering with the JS7 - License.
• Technically the block instruction checks the first available Subagent of a Subagent Cluster. This Subagent will be used for subsequent jobs within the block instruction.
  • The underlying use case is a situation when jobs in a workflow create temporary files that should be picked up by successor jobs. If successor jobs were executed with different Subagents on different servers then they might not find files created by predecessor jobs.
  • If the Subagent used for the first job of the StickySubagent Instructions becomes unavailable for subsequent jobs then the order will be put to the BLOCKED state. Uses Users can decide to cancel the order or to make the Subagent available later on. A BLOCKED order will continue execution when the Subagent becomes available.
  • Jobs within a StickySubagent Instruction block can be assigned the predetermined Subagent or they can be assigned Standalone Agents and Subagent Clusters unrelated to the StickySubagent Instruction.

...

Download example (upload .json): pdfAgentClusterStickySubagent.workflow.json

...

Assigning the Subagent Cluster to the StickySubagent Instruction

The workflow editor is used to add a StickySubagent Instruction as shown:

...

• The StickySubagent Instruction is assigned the Subagent Cluster active-active-all-agents from the AgentCluster001 cluster.
• The jobs inside the StickySubagent Instruction are executed on the same Subagent that is a member of the active-active-all-agents Subagent Cluster.
  • Users are free to exempt individual jobs from using the same Subagent and instead to be executed execute the job for example on a Standalone AgentsAgent. 

...

Assigning an Agent Cluster

...

to a Job Instruction

Individual jobs inside the StickySubagent Instruction are assigned Subagents like this:

• The Select Agent or Subagent Expression radio  radio button is selected and the same AgentCluster001 cluster as for the StickySubagent Instruction is selected.
• The Subagent Cluster ID Expression is specified: the $js7ForkListSubagentId variable is automatically available at run-time and holds the identification of the respective Subagent for execution of the jobactive-active-all-agents is selected that corresponds to the Subagent Cluster assigned the StickySubagent Instruction.
  
  

Dynamic Assignment of Subagent Cluster

...

• The StickySubagent Instruction is assigned a Subagent Expression.
  • This includes to select an Agent Cluster.
  • This includes to specify an expression, for this example the workflow variable $subagent_cluster, that carries the name of the Subagent Cluster.
• The StickySubagent Instruction includes a number of jobs that should be executed on the same Subagent of the given Subagent Cluster.
  
  

Error Handling

The same error handling applies as for the JS7 - ForkList-Join Instruction.

Resources

...

StickySubagent Instruction selects the first available Subagent of the given Subagent Cluster. Subagents not available at the point in time of execution of the instruction are not considered.

• If the Subagent used for the first job of the StickySubagent Instructions becomes unavailable for subsequent jobs then the order will be put to the BLOCKED state.
• Users can decide to cancel the order or to make the Subagent available later on. A BLOCKED order will continue execution when the Subagent becomes available.

Standard error handling applies to jobs within the StickySubagent Instruction.

• This includes use of the JS7 - Retry Instruction and JS7 - Try-Catch Instruction.
• This includes use of the JS7 - Fail Instruction and JS7 - Finish Instruction.

Resources

• JS7 - ForkList-Join Instruction for Agent Clusters
• JS7 - Order State Transitions
• JS7 - How To - Error Handling

...