NOOP task: missing builder class
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 86/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- java
- Domain
- developer-experience
Research direction
Start in conductor-client/src/main/java/com/netflix/conductor/sdk/workflow/def/tasks/ and compare existing Task subclasses with TaskType.NOOP in the SDK enum. Run the project’s Java build and tests after adding the builder; done means users can instantiate new Noop("noop_ref") and it represents a NOOP workflow task without manual WorkflowTask construction.
Written by the indexing model from the issue text.
Description
Summary
TaskType.NOOP exists in the SDK enum but there is no Noop builder class in
conductor-client/src/main/java/com/netflix/conductor/sdk/workflow/def/tasks/.
Users cannot create a NOOP workflow task using the fluent SDK API — they must fall
back to constructing a raw WorkflowTask manually.
Server baseline
Conductor 3.32.0-rc.9
Evidence
Static: TaskType.NOOP is in the enum; no Noop.java file exists under
conductor-client/…/def/tasks/.
Live (2026-07-16): A raw WorkflowTask with "type": "NOOP" was registered
and executed against Conductor OSS 3.32.0-rc.9 at http://loki.local:8080. The workflow
completed successfully, confirming the server supports NOOP — the gap is SDK-only.
Expected behaviour
Users should be able to write:
new Noop("noop_ref")
Proposed fix
public class Noop extends Task<Noop> {
public Noop(String taskReferenceName) {
super(taskReferenceName, TaskType.NOOP);
}
}
No updateWorkflowTask override required — NOOP has no inputParameters.
Related
Discovered during systematic SDK audit against Conductor OSS 3.32.0-rc.9 server.
Same gap exists in the Python SDK (conductor-oss/python-sdk#430).
- Dominant language
- Java
- Stars
- 15
- Forks
- 10
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from conductor-oss/java-sdk
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
conductor-oss/java-sdk#135 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
conductor-oss/java-sdk#133 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
conductor-oss/java-sdk#132 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
conductor-oss/java-sdk#131 ·
-
Http task: no fluent connectionTimeout() builder methodMay be free again @kowser-orkes claimed this 70 days ago, and no pull request is open. Openbug
conductor-oss/java-sdk#134 · 1 comment · 2 assignees ·
All issues in conductor-oss/java-sdk
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
apache/rocketmq-dashboard#5358 ·
Maintainers usually reply within 3 days
-
area:cpan-port area:database bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
fglock/PerlOnJava#1605 ·
Maintainers usually reply within 1 day
-
1.0.0-rc2
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wso2/dpdp-accelerator#377 ·
Maintainers usually reply within 1 day
-
area/dependencies backport/26.4 kind/cve severity/high source/scan-dependencies status/triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day