## TL;DR

On Vald upsert ALREADY_EXISTS, do not retry: the ID and vector pair is already inserted, so update the payload or move on. Match your request vector dimension exactly to the agent config to avoid INVALID_ARGUMENT, and never send an empty ID.

## Steps

1. On Vald upsert ALREADY_EXISTS, do not retry: the ID and vector pair is already inserted, so update the payload or move on.

2. Match your request vector dimension exactly to the agent config to avoid INVALID_ARGUMENT, and never send an empty ID.

## When to use

You are seeing this: Also documents that INVALID_ARGUMENT fires when the request vector dimension differs from the agent config or the ID is empty. Use this skill when you run into "Vald upsert ALREADY_EXISTS means already stored, do not retry".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

## Edge cases

- Also documents that INVALID_ARGUMENT fires when the request vector dimension differs from the agent config or the ID is empty.