Summary
The Http builder class has a fluent readTimeout(int) method but no corresponding
connectionTimeout(int) method. Users who need to set connectionTimeOut must break
the fluent builder chain by calling getHttpRequest().setConnectionTimeOut(n) directly.
Server baseline
Conductor 3.32.0-rc.9
Evidence
Static:
Http.java:84 — public Http readTimeout(int readTimeout) exists
Http.Input (line 229-239) — has connectionTimeOut field, getter, setter
- No
connectionTimeout() fluent method on Http class
Live (2026-07-16): Server correctly reads connectionTimeOut from http_request
(workflow registered with connectionTimeOut: 3000 was accepted by Conductor OSS 3.32.0-rc.9).
Inconsistency
// readTimeout — has fluent method ✓
Http http = new Http("task_ref")
.url("https://example.com")
.method(HttpMethod.GET)
.readTimeout(5000);
// connectionTimeOut — NO fluent method ✗ (must break builder chain)
http.getHttpRequest().setConnectionTimeOut(3000);
Proposed fix
// Http.java — add alongside readTimeout()
public Http connectionTimeout(int connectionTimeout) {
this.httpRequest.setConnectionTimeOut(connectionTimeout);
return this;
}
Related
Discovered during systematic SDK audit against Conductor OSS 3.32.0-rc.9.
Summary
The
Httpbuilder class has a fluentreadTimeout(int)method but no correspondingconnectionTimeout(int)method. Users who need to setconnectionTimeOutmust breakthe fluent builder chain by calling
getHttpRequest().setConnectionTimeOut(n)directly.Server baseline
Conductor 3.32.0-rc.9
Evidence
Static:
Http.java:84—public Http readTimeout(int readTimeout)existsHttp.Input(line 229-239) — hasconnectionTimeOutfield, getter, setterconnectionTimeout()fluent method onHttpclassLive (2026-07-16): Server correctly reads
connectionTimeOutfromhttp_request(workflow registered with
connectionTimeOut: 3000was accepted by Conductor OSS 3.32.0-rc.9).Inconsistency
Proposed fix
Related
Discovered during systematic SDK audit against Conductor OSS 3.32.0-rc.9.