開發者平台
OpenAI Java SDK 4.58 Recognizes Incomplete Web Search Calls, Rounding Out Responses Status Handling
OpenAI’s official Java SDK 4.58.0 adds support for recognizing the `incomplete` status of web search calls, preventing applications from treating interrupted search steps as successful or unknown values. The release is available on Maven Central, but projects still using the discontinued Spring Boot 2 starter cannot directly adopt the updated package.
OpenAI has released Java SDK 4.58.0. The main API change enables the type model to recognize the `incomplete` status for web search calls. Although this may appear to be only a schema update, it directly affects Java services that use the Responses API and treat search as an agent tool step. A search call may remain incomplete because of limits, timeouts, or workflow termination. If an application handles only successful and failed outcomes, it may continue generating without search content, write the result to a cache, or even mark an incomplete answer as complete.
The new version lets clients incorporate this status into explicit control flows—for example, to retry, narrow the query, retain partial results, switch data sources, or report upstream that human intervention is required. For long-running agents, it also helps distinguish between a tool that returned insufficient data and a transport-layer exception. Monitoring systems can track an incomplete-call rate instead of collapsing every case into a generic error. After upgrading, engineers should still review their `switch` statements, serialization, persistence, and event replay logic: the SDK’s ability to parse the new status does not mean the application’s business logic has defined how to handle it.
Version 4.58.0 has been published to Maven Central under the Apache License 2.0. Gradle or Maven projects can specify `com.openai:openai-java:4.58.0` directly. The official repository also notes that the framework-agnostic package currently maintains Java 8 as its minimum version. However, support and updates for `openai-java-spring-boot-starter` ended with version 4.45.0. Spring Boot 2 projects that still depend on the starter cannot assume that simply updating the version number will provide the same integration. They should instead depend directly on the core SDK and register `OpenAIClient` themselves.
This is not an upgrade to model capabilities or search quality, and no new performance benchmarks have been published. Its value lies in aligning the tool state machine with actual server responses. The next points to watch are whether SDKs for other languages adopt a consistent enum and whether OpenAI provides further documentation on the reason codes that trigger `incomplete` and the recommended retry strategies.