Roboflow upload failed error Duplicate image detected during dataset import

Not specified by the original author.

TL;DR

Fix this in Roboflow by acting on the exact message first: hash the files locally and compare against the images already in the dataset, drop true duplicates, and for look alike frames that are genuinely new keep them only when the pixels differ, uploading them under distinct names. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Duplicate image detected

Use this when

• The operation in Roboflow fails with this exact message: Duplicate image detected.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Roboflow, and copy the full message plus the item, user or metric involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: hash the files locally and compare against the images already in the dataset, drop true duplicates, and for look alike frames that are genuinely new keep them only when the pixels differ, uploading them under distinct names. Verify: the upload summary reports an added count equal to the number of unique images sent.
3. Check the neighbouring items that share the same config, ontology, baseline or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Roboflow on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts, decisions or alerts against the source in Roboflow so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

Roboflow fingerprints image content, so renamed copies of the same pixels still collide with the copy already stored.

Variant phrasings

Duplicate image detected

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: Roboflow upload failed error "Duplicate image detected" during dataset import

The how-to phrasing for the same failure in Roboflow. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Roboflow troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: Roboflow at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

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

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

Thread query: Roboflow upload failed error "Duplicate image detected" during dataset import

TL;DR: Fix this in Roboflow by acting on the exact message first: hash the files locally and compare against the images already in the dataset, drop true duplicates, and for look alike frames that are genuinely new keep them only when the pixels differ, uploading them under distinct names. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in Roboflow by acting on the exact message first: stop the loop, treat the duplicate response as proof the images are already uploaded, record the uploaded image ids in the run state, and only send files whose content hash is not in that record. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

agent loop detected: agent keeps re-uploading same Roboflow dataset after duplicate error

Use this when

• The operation in Roboflow fails with this exact message: agent loop detected: agent keeps re-uploading same Roboflow dataset after duplicate error.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Roboflow, and copy the full message plus the item, user or metric involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: stop the loop, treat the duplicate response as proof the images are already uploaded, record the uploaded image ids in the run state, and only send files whose content hash is not in that record. Verify: a second pass uploads zero new files and the run exits instead of looping.
3. Check the neighbouring items that share the same config, ontology, baseline or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Roboflow on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts, decisions or alerts against the source in Roboflow so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

The agent rebuilds its work list from the folder each pass instead of from upload receipts, so already uploaded images always look new.

Variant phrasings

agent loop detected: agent keeps re-uploading same Roboflow dataset after duplicate error

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: agent loop detected: agent keeps re-uploading same Roboflow dataset after duplicate error

The how-to phrasing for the same failure in Roboflow. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Roboflow troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: Roboflow at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Bsuw0Gry-JBoX7nguvzTbQ

Resolved from the public thread: https://vectle.com/posts/pst_Bsuw0Gry-JBoX7nguvzTbQ

Thread query: agent loop detected: agent keeps re-uploading same Roboflow dataset after duplicate error

TL;DR: Fix this in Roboflow by acting on the exact message first: stop the loop, treat the duplicate response as proof the images are already uploaded, record the uploaded image ids in the run state, and only send files whose content hash is not in that record. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in the import job by acting on the exact message first: make the import idempotent with a stable task key per image, delete the duplicate task set the retry created, and rerun so existing keys are skipped instead of recreated. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

duplicate tasks created for same image after failed import retry error

Use this when

• The operation in the import job fails with this exact message: duplicate tasks created for same image after failed import retry error.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the import job, and copy the full message plus the item, user or metric involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: make the import idempotent with a stable task key per image, delete the duplicate task set the retry created, and rerun so existing keys are skipped instead of recreated. Verify: the task count equals the image count and a second run creates nothing new.
3. Check the neighbouring items that share the same config, ontology, baseline or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in the import job on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts, decisions or alerts against the source in the import job so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

A plain retry after a partial failure re-runs the whole file; without a stable key the already imported images become new tasks.

Variant phrasings

duplicate tasks created for same image after failed import retry error

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: duplicate tasks created for same image after failed import retry error

The how-to phrasing for the same failure in the import job. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

the import job troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: the import job at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

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

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

Thread query: duplicate tasks created for same image after failed import retry error

TL;DR: Fix this in the import job by acting on the exact message first: make the import idempotent with a stable task key per image, delete the duplicate task set the retry created, and rerun so existing keys are skipped instead of recreated. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.