alibaba/spring-ai-alibaba · warning · ResponseStatusException

Thread already exists:

Error message

Thread already exists: 

What it means

ThreadController.createThreadWithId throws 400 BAD_REQUEST 'Thread already exists: <threadId>' when the pre-check findThreadOrThrow succeeds, meaning a thread with that ID already exists for the app/user. Client-supplied thread IDs are treated as create-only: use PUT semantics elsewhere or delete first.

Source

Thrown at spring-ai-alibaba-studio/src/main/java/com/alibaba/cloud/ai/agent/studio/controller/ThreadController.java:181

	 */
	@PostMapping("/apps/{appName}/users/{userId}/threads/{threadId}")
	public Thread createThreadWithId(
			@PathVariable String appName,
			@PathVariable String userId,
			@PathVariable String threadId,
			@RequestBody(required = false) Map<String, Object> state) {
		log.info(
				"Request received for POST /apps/{}/users/{}/threads/{} with state: {}",
				appName,
				userId,
				threadId,
				state);

		try {
			findThreadOrThrow(appName, userId, threadId);

			log.warn("Attempted to create thread with existing ID: {}", threadId);
			throw new ResponseStatusException(
					HttpStatus.BAD_REQUEST, "Thread already exists: " + threadId);
		}
		catch (ResponseStatusException e) {

			if (e.getStatusCode() != HttpStatus.NOT_FOUND) {
				throw e;
			}

			log.info("Thread {} not found, proceeding with creation.", threadId);
		}

		Map<String, Object> initialState = (state != null) ? state : Collections.emptyMap();
		try {
			Thread createdThread =
					threadService
							.createThread(appName, userId, new ConcurrentHashMap<>(initialState), threadId)
							.block();

View on GitHub (pinned to f82da0b50f)

Solutions

1. GET the thread first and skip creation if it already exists (idempotent client logic)
2. DELETE the existing thread then POST again if a fresh thread is intended
3. Use POST /apps/{appName}/users/{userId}/threads (no ID) to get a generated unique ID
4. Generate thread IDs with UUID.randomUUID() so collisions cannot occur
5. Handle the 400 status in your HTTP client and treat it as 'already created'

Example fix

// before
given threadId="abc": POST /apps/app/users/u/threads/abc  // 400 if exists
// after
try { POST .../threads/abc } catch (HttpClientErrorException.BadRequest e) {
    return GET .../threads/abc; // reuse existing
}

boolean exists;
try { GET "/apps/{a}/users/{u}/threads/{t}"; exists = true; } catch (HttpClientErrorException.NotFound e) { exists = false; }
// only POST when !exists

try { return create(id); } catch (HttpClientErrorException.BadRequest e) { return get(id); } // idempotent create-or-get

When it happens

Trigger: POST to /apps/{appName}/users/{userId}/threads/{threadId} where the (appName, userId, threadId) triple already exists; duplicate form submissions; retry of an already-successful creation; two clients racing to create the same ID.

Common situations: Browser refresh resubmitting a POST; cron/setup scripts that run idempotently but POST with fixed IDs; test fixtures creating the same threadId across runs without cleanup.

Understand the failure class

Background: "already exists" / EEXIST / FileAlreadyExistsException: what the 'file already exists' error means and how to fix it — this error's family across 37 libraries.

Related errors

• Thread already exists:
• Failed to create thread
• Thread not found: appName=%s, userId=%s, threadId=%s
• Thread found but belongs to a different app/user.
• Failed to create thread (null result)

AI-assisted analysis of alibaba/spring-ai-alibaba@f82da0b50f (2026-09-09). Data as JSON: /api/errors/e5315007a69efec8. Report an issue: GitHub.