Summary
TaskType.HUMAN exists in the SDK enum but there is no Human builder class in
conductor-client/…/def/tasks/. Users cannot create a HUMAN task using the fluent SDK API.
Server baseline
Conductor 3.32.0-rc.9
Evidence
Static: TaskType.HUMAN is in the enum; no Human.java file under
conductor-client/…/def/tasks/.
Live (2026-07-16): A raw WorkflowTask with "type": "HUMAN" was registered
and executed against Conductor OSS 3.32.0-rc.9. The workflow entered RUNNING state
awaiting human signal (expected behavior) — server accepts HUMAN tasks, gap is SDK-only.
Expected behaviour
new Human("human_approval_ref")
Proposed fix
public class Human extends Task<Human> {
public Human(String taskReferenceName) {
super(taskReferenceName, TaskType.HUMAN);
}
}
No updateWorkflowTask override required — HUMAN has no required inputParameters.
Related
Discovered during systematic SDK audit against Conductor OSS 3.32.0-rc.9.
Summary
TaskType.HUMANexists in the SDK enum but there is noHumanbuilder class inconductor-client/…/def/tasks/. Users cannot create a HUMAN task using the fluent SDK API.Server baseline
Conductor 3.32.0-rc.9
Evidence
Static:
TaskType.HUMANis in the enum; noHuman.javafile underconductor-client/…/def/tasks/.Live (2026-07-16): A raw
WorkflowTaskwith"type": "HUMAN"was registeredand executed against Conductor OSS 3.32.0-rc.9. The workflow entered RUNNING state
awaiting human signal (expected behavior) — server accepts HUMAN tasks, gap is SDK-only.
Expected behaviour
Proposed fix
No
updateWorkflowTaskoverride required — HUMAN has no requiredinputParameters.Related
Discovered during systematic SDK audit against Conductor OSS 3.32.0-rc.9.