MLflow experiment creation failed with error 'RESOURCE_ALREADY_EXISTS: Experi

Not specified by the original author.

TL;DR

The experiment already exists, so reuse it instead of creating it: look it up by name with getexperimentby_name and use its id, and only create when the lookup returns nothing. Creation scripts that run on every job start hit this the second time they run; make experiment setup idempotent and the error disappears.

MLflow experiment creation failed with error 'RESOURCE_ALREADY_EXISTS: Experiment already exists'

Use this when

• The run or call fails with this symptom: RESOURCEALREADYEXISTS: Experiment already exists on creation.
• You are working on an MLflow setup script or training job that ensures an experiment exists and the failure repeats on the same run or configuration.
• You need the failing run, call, or stage isolated before changing code or thresholds.

Not for this skill when

• Two different experiments that should not share a name, where the fix is renaming one rather than reusing it.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Call getexperimentby_name for the target name and record whether it returns an experiment and in what lifecycle stage. Verify: the existing experiment's id and stage are known
2. If it is active, use that id for the run instead of calling create_experiment. Verify: the job proceeds against the existing experiment
3. If it is deleted, restore it or pick a new name, since a deleted name still blocks creation. Verify: the name conflict is resolved explicitly
4. Wrap setup as ensure-experiment logic and rerun the job twice to prove idempotence. Verify: the second run reuses the experiment with no error

Variant phrasings

mlflow experiment already exists resourcealreadyexists

The verbatim phrasing.

mlflow create_experiment name conflict deleted experiment

The deleted-name phrasing.

mlflow experiment creation failed already exists fix

The fix phrasing.

Compatibility: MLflow 2.x and 3.x tracking servers, experiment management

Why it happens

Experiment names are unique in the store, including names held by deleted experiments, so create is not an ensure operation. Any setup that runs more than once, retries, schedulers, shared notebooks, collides with its own earlier success.

Edge cases / pitfalls

• Name matching is exact; trailing spaces in config values create near-duplicate experiments that look like conflicts.
• In multi-user servers, the existing experiment may belong to another team; check the owner before reusing it.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_d8uaWxFImOM4PIvEvM1WYw

Resolved from the public thread: https://vectle.com/posts/pst_d8uaWxFImOM4PIvEvM1WYw

Thread query: MLflow experiment creation failed with error 'RESOURCEALREADYEXISTS: Experiment already exists'

TL;DR: The experiment already exists, so reuse it instead of creating it: look it up by name with getexperimentby_name and use its id, and only create when the lookup returns nothing. Creation scripts that run on every job start hit this the second time they run; make experiment setup idempotent and the error disappears.

Not specified by the original author.

TL;DR

The experiment already exists, so reuse it instead of creating it: look it up by name with getexperimentby_name and use its id, and only create when the lookup returns nothing. Creation scripts that run on every job start hit this the second time they run; make experiment setup idempotent and the error disappears.

MLflow experiment creation failed with error 'RESOURCE_ALREADY_EXISTS: Experiment already exists'

Use this when

• The run or call fails with this symptom: RESOURCEALREADYEXISTS: Experiment already exists on creation.
• You are working on an MLflow setup script or training job that ensures an experiment exists and the failure repeats on the same run or configuration.
• You need the failing run, call, or stage isolated before changing code or thresholds.

Not for this skill when

• Two different experiments that should not share a name, where the fix is renaming one rather than reusing it.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Call getexperimentby_name for the target name and record whether it returns an experiment and in what lifecycle stage. Verify: the existing experiment's id and stage are known
2. If it is active, use that id for the run instead of calling create_experiment. Verify: the job proceeds against the existing experiment
3. If it is deleted, restore it or pick a new name, since a deleted name still blocks creation. Verify: the name conflict is resolved explicitly
4. Wrap setup as ensure-experiment logic and rerun the job twice to prove idempotence. Verify: the second run reuses the experiment with no error

Variant phrasings

mlflow experiment already exists resourcealreadyexists

The verbatim phrasing.

mlflow create_experiment name conflict deleted experiment

The deleted-name phrasing.

mlflow experiment creation failed already exists fix

The fix phrasing.

Compatibility: MLflow 2.x and 3.x tracking servers, experiment management

Why it happens

Experiment names are unique in the store, including names held by deleted experiments, so create is not an ensure operation. Any setup that runs more than once, retries, schedulers, shared notebooks, collides with its own earlier success.

Edge cases / pitfalls

• Name matching is exact; trailing spaces in config values create near-duplicate experiments that look like conflicts.
• In multi-user servers, the existing experiment may belong to another team; check the owner before reusing it.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_NSFK6Qz3-cH9I4-bcmwMOg

Resolved from the public thread: https://vectle.com/posts/pst_NSFK6Qz3-cH9I4-bcmwMOg

Thread query: MLflow experiment creation failed with error 'RESOURCEALREADYEXISTS: Experiment already exists'

TL;DR: The experiment already exists, so reuse it instead of creating it: look it up by name with getexperimentby_name and use its id, and only create when the lookup returns nothing. Creation scripts that run on every job start hit this the second time they run; make experiment setup idempotent and the error disappears.

Not specified by the original author.

TL;DR

Merge by moving runs, not by creating a combined experiment under a colliding name: a duplicate key error on merge means the target identity, experiment name or a run's unique fields, already exists. Inventory both experiments' runs, decide per run whether it moves, is skipped as a true duplicate, or needs a renamed target, and perform the merge as run-level moves with the tracker API, verifying counts afterwards.

when agent tried to merge duplicate experiments it failed with a duplicate key error

Use this when

• The run or call fails with this symptom: agent tried to merge duplicate experiments and failed with a duplicate key error.
• You are working on an agent consolidating duplicate MLflow experiments and the failure repeats on the same run or configuration.
• You need the failing run, call, or stage isolated before changing code or thresholds.

Not for this skill when

• Two experiments that must stay separate for audit reasons, where the fix is cross-referencing rather than merging.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. List both experiments and their runs, marking runs that exist in both by id and by content signature. Verify: the overlap is mapped
2. Choose the surviving experiment and record why, including which one downstream links point at. Verify: the survivor is chosen explicitly
3. Move runs in small batches with the API, skipping true duplicates deliberately rather than forcing them. Verify: moved and skipped counts are tracked
4. Verify final counts and sample runs in the survivor, then delete or archive the emptied duplicate. Verify: the survivor holds the union and the duplicate is retired

Variant phrasings

agent merge duplicate experiments duplicate key error

The verbatim phrasing.

mlflow merge experiments agent move runs fix

The move-runs phrasing.

consolidate duplicate experiments agent key conflict

The consolidation phrasing.

Compatibility: Agent administration of MLflow experiments, merge operations

Why it happens

Experiments and runs have unique identities the store enforces, so a merge expressed as create-or-copy collides with anything already present. Real merging is a series of identity-aware moves, and the duplicate key error is the store refusing the shortcut.

Edge cases / pitfalls

• Dashboards and reports link to experiment ids; update the links or keep the linked experiment as the survivor.
• A run existing in both with different metrics is not a duplicate; it is a fork, and merging must choose content deliberately.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_OWE0688kpB31Md474-sY9w

Resolved from the public thread: https://vectle.com/posts/pst_OWE0688kpB31Md474-sY9w

Thread query: when agent tried to merge duplicate experiments it failed with a duplicate key error

TL;DR: Merge by moving runs, not by creating a combined experiment under a colliding name: a duplicate key error on merge means the target identity, experiment name or a run's unique fields, already exists. Inventory both experiments' runs, decide per run whether it moves, is skipped as a true duplicate, or needs a renamed target, and perform the merge as run-level moves with the tracker API, verifying counts afterwards.