## TL;DR
Rename or reuse deliberately: a SageMaker trial component with that name already exists in the trial, so either attach the new work to the existing component or generate a unique component name per attempt. Trial component names are unique within a trial in SageMaker Experiments. A retry that reuses the name of a component created by the first attempt collides with its own predecessor.

```text
SageMaker experiment failed error "ValidationException: trial component name already exists"
```

## Use this when
- The check or run fails with this symptom: a SageMaker experiment fails with ValidationException trial component name already exists.
- You are working on a SageMaker Experiments trial receiving trial components from a training or processing job and the failure repeats on the same data or configuration.
- You need the failing run, call, or stage isolated before changing code or thresholds.

## Not for this skill when
- A name collision with a component from a genuinely different job, where the trial organisation, not the naming, needs review.
- The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

## Steps
1. List the trial components in the trial and find the existing component with that name. Verify: the earlier component and its status are visible
2. Decide whether the new run should replace, attach to, or sit beside the existing component. Verify: the intent is chosen before any rename
3. Generate component names with a run specific suffix, such as the job name plus a timestamp or attempt id. Verify: repeated submissions produce distinct names
4. Resubmit the job. Verify: a new trial component is created and associated with the trial
5. Check the trial view. Verify: both components appear with their own metrics where intended

## Variant phrasings
### sagemaker trial component name already exists ValidationException
The shorter phrasing focused on the named failure.
### sagemaker experiment failed component name exists
The symptom phrasing a searcher tries next.
### sagemaker trial component naming fix
The variant naming the failing stage or tool directly.

Compatibility: SageMaker Experiments trials and trial components, training and processing job integration

## Why it happens
SageMaker creates a trial component per job execution and enforces unique names inside a trial. Retry logic, whether from a pipeline step or a human rerun with the same job name, replays the same component name into the same trial and is rejected as a validation error.

## Edge cases / pitfalls
- Deleting the existing component to reuse its name destroys the first attempt record; rename the new one instead.
- Automatic retries in pipelines should carry the attempt number into the job name so the component name follows.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_U4efkjTjS4-VY9iKOPAUhA