Skip to main content

Receives executor task command

SUB 

{agent-base-topic}/exec/command

The selected executor receives the task assignment or forwarded signal on its own exec/command. The Swarm Leader sets the command's sender to its own agent-id and leaves every other field unchanged. An admitted member flies a start-task, or applies a signal-task, whose sender is the elected Swarm Leader's agent-id locally; it hands any other sender's start-task to the Swarm Unit as member task ingress, and handles any other sender's signal-task as a direct signal, so an assignment is never rebroadcast as new ingress. The sender is any non-empty string; a command without a sender is ingress. A start-task still needs the executor's matching bid reservation and otherwise fails with 'inactive task', whoever published it; a signal-task from any publisher whose sender equals the elected Swarm Leader's agent-id is applied as a forwarded signal, because the bus does not authenticate publishers. A command naming another agent-id is ignored. The executor fails a command on its own execution boundary with fail-reason 'parsing error', 'invalid task payload', 'task-already-running', 'inactive task' or 'unsupported signal'.

MQTT​

QoS1
retainfalse

Message message​

Message message​

Message message​

Receives executor task command
{
"task": {
"params": {
"swarm": false,
"agent-count": 1
}
},
"parent-task-uuid": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"parent-com-uuid": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
}