High severity intermediate · Fix: 2-5 min

wandb.errors.CommError

wandb.errors.CommError: Artifact version not found

What this error means
Weights & Biases raises a 'artifact not found version' error when the specified artifact version does not exist or is inaccessible in the project.

Stack trace

traceback
wandb.errors.CommError: Artifact version 'v1' not found for artifact 'dataset:latest'
  File "/usr/local/lib/python3.9/site-packages/wandb/sdk/internal/internal_api.py", line 1234, in get_artifact
    raise CommError(f"Artifact version '{version}' not found for artifact '{name}'")
QUICK FIX
Confirm the artifact name and version exist in your WandB project and correct any typos before calling use_artifact.

Why it happens

This error occurs when the code requests a specific artifact version that does not exist in the WandB project or the user lacks permission to access it. It can also happen if the artifact name or version string is misspelled or if the artifact has not been logged yet.

Detection

Check for wandb.errors.CommError exceptions when calling wandb.use_artifact or wandb.Api().artifact and verify the artifact name and version exist in the WandB UI before proceeding.

Causes & fixes

1

Requested artifact version does not exist in the WandB project

✓ Fix

Verify the artifact version string is correct and that the artifact has been logged with that version in the WandB project.

2

Artifact name or version string is misspelled or incorrectly formatted

✓ Fix

Double-check the artifact name and version string for typos or incorrect casing and correct them in the code.

3

User does not have permission to access the specified artifact version

✓ Fix

Ensure the WandB API key used has read access to the project and artifact version, or request access from the project owner.

4

Artifact has not been logged yet or was deleted

✓ Fix

Confirm the artifact was successfully logged and not deleted; if missing, log the artifact before attempting to use it.

Code: broken vs fixed

Broken - triggers the error
python
import wandb

run = wandb.init(project="my-project")
artifact = run.use_artifact('dataset:latest')  # This line triggers the artifact not found version error
print(artifact)
Fixed - works correctly
python
import os
import wandb

os.environ['WANDB_API_KEY'] = os.environ.get('WANDB_API_KEY')  # Ensure API key is set

run = wandb.init(project="my-project")
# Specify exact existing artifact version, e.g. 'dataset:v1'
artifact = run.use_artifact('dataset:v1')  # Fixed: use correct artifact version
print(artifact)
Specified the exact existing artifact version string to avoid requesting a non-existent version, preventing the error.

Workaround

Wrap the use_artifact call in try/except wandb.errors.CommError, and if caught, list available artifact versions via wandb.Api() to select a valid version dynamically.

Prevention

Implement validation logic to check artifact existence and versions via wandb.Api() before use, and automate artifact version management to avoid referencing missing versions.

Python 3.7+ · wandb >=0.12.0 · tested on 0.15.x
Verified 2026-04
Verify ↗

Community Notes

No notes yetBe the first to share a version-specific fix or tip.