TaskType enum missing AGENT, GET_AGENT_CARD, CANCEL_AGENT, PULL_WORKFLOW_MESSAGES
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
Research direction
Compare the SDK's TaskType.java with the server's TaskType.java at Conductor 3.32.0-rc.9, starting with the SDK enum entry that currently ends at CALL_MCP_TOOL. Verify that TaskType.of("AGENT") and the other three names resolve to their corresponding enum values, with no builder work required until the agent task API is stable.
Written by the indexing model from the issue text.
Description
Summary
Four task types added to the Conductor server in 3.32.0-rc.9 (PR conductor-oss/conductor#1288)
are absent from the SDK's TaskType enum. Calling TaskType.of("AGENT") silently returns
USER_DEFINED instead of the correct value.
Server baseline
Conductor 3.32.0-rc.9
Missing values
The server's TaskType.java has:
PULL_WORKFLOW_MESSAGES,
AGENT,
GET_AGENT_CARD,
CANCEL_AGENT;
The SDK's TaskType.java stops at CALL_MCP_TOOL — all four values are absent.
Impact
TaskType.of("AGENT")returnsUSER_DEFINED— silently wrong- No builder classes can be typed to these task types
- SDK users writing AGENT workflows must hard-code raw strings
Evidence
Static: Compared server TaskType.java against SDK TaskType.java.
Live (2026-07-16): A raw WorkflowTask with "type": "AGENT" was registered
against Conductor OSS 3.32.0-rc.9. Server accepted the definition, confirming the type is
valid server-side — the gap is SDK-only.
Proposed fix
Add to the SDK TaskType enum:
PULL_WORKFLOW_MESSAGES,
AGENT,
GET_AGENT_CARD,
CANCEL_AGENT;
Builder classes for AGENT, GET_AGENT_CARD, and CANCEL_AGENT should follow once the
agent task API is stable.
Related
Discovered during systematic SDK audit against Conductor OSS 3.32.0-rc.9.
Same gap exists in the Python SDK (conductor-oss/python-sdk#431).
Server PR: conductor-oss/conductor#1288
- 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 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 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
conductor-oss/java-sdk#130 ·
-
Http task: no fluent connectionTimeout() builder methodMay be free again @kowser-orkes claimed this 71 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 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
aoqia194/leaf-loader#19 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
apache/streampark#4521 ·
-
Update license yearOpen0 - Backlog 1 - Ready documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
cbor
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
FasterXML/jackson-dataformats-binary#844 ·
Maintainers usually reply within 1 day