Hyperproof evidence upload error proof already exists for this control duplicate

Not specified by the original author.

TL;DR

Fix this in Hyperproof by acting on the exact problem first: open the control in Hyperproof, find the existing proof with the same name and date, link that proof to the requirement instead of uploading a copy, and if the new file is a newer version, replace the old proof as a new version with a note saying it supersedes the earlier one, then confirm the control shows satisfied without a duplicate. Do not rerun the whole job or collection unchanged, because the same inputs produce the same failure. Prove the fix on one control, account or batch first, then rerun the full scope and reconcile the counts.

proof already exists for this control - duplicate rejected

Use this when

• The operation in Hyperproof fails with this exact message or symptom: proof already exists for this control - duplicate rejected.
• The same failure repeats on retry with unchanged inputs.
• An audit, evidence package or compliance review is blocked until this item completes.

Not for this skill when

• The message is an outage notice from the platform. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with an auditor judgment or a control design choice. That is a review discussion, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Hyperproof, and copy the full message plus the control, account or item involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: open the control in Hyperproof, find the existing proof with the same name and date, link that proof to the requirement instead of uploading a copy, and if the new file is a newer version, replace the old proof as a new version with a note saying it supersedes the earlier one, then confirm the control shows satisfied without a duplicate. Verify: the smallest failing scope now completes, or the named control, account or item behaves as the fix predicts.
3. Check the neighbouring controls, accounts or items that share the same connection, mapping or owner, 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 Hyperproof 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 or status against the source in Hyperproof 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 problem, the fix applied and the evidence of success.

Why it happens

Hyperproof deduplicates proof per control, so a second upload of the same evidence is rejected even when the underlying requirement is already met by the first copy.

Variant phrasings

proof already exists for this control - duplicate rejected

The verbatim form searchers paste from the console, ticket or audit request. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - Hyperproof evidence upload error "proof already exists for this control" duplicate rejected

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

Hyperproof 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.

Edge cases

• If the fix works on the small scope but the full rerun still fails on a different item, treat that item as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If evidence was already sent to an auditor in the wrong state, correct the record with a dated note explaining what changed, rather than silently replacing files in the package.
• If two settings or mappings could both produce this symptom, change one at a time and retest the small scope after each change, so the working fix is known rather than guessed.

Compatibility: Hyperproof at current versions, plus the admin console or API the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

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

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

Thread query: Hyperproof evidence upload error "proof already exists for this control" duplicate rejected

TL;DR: Fix this in Hyperproof by acting on the exact problem first: open the control in Hyperproof, find the existing proof with the same name and date, link that proof to the requirement instead of uploading a copy, and if the new file is a newer version, replace the old proof as a new version with a note saying it supersedes the earlier one, then confirm the control shows satisfied without a duplicate. Do not rerun the whole job or collection unchanged, because the same inputs produce the same failure. Prove the fix on one control, account or batch first, then rerun the full scope and reconcile the

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 questionnaire portal upload by acting on the exact message first: add backoff before any upload retry, name each upload with a key built from the questionnaire ID and file hash, and check the portal file list for that key before uploading again so a retry reuses the first upload. 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.

questionnaire agent retried portal upload without backoff file flagged as duplicate

Use this when

• The operation in the questionnaire portal upload fails with this exact message: questionnaire agent retried portal upload without backoff file flagged as duplicate.
• 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 questionnaire portal upload, and copy the full message plus the questionnaire, answer or evidence item 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: add backoff before any upload retry, name each upload with a key built from the questionnaire ID and file hash, and check the portal file list for that key before uploading again so a retry reuses the first upload. Verify: the portal holds one copy of the file and the duplicate flag is cleared.
3. Check the neighbouring items that share the same config, template, feed 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. Compare the result counts, decisions or alerts against the source in the questionnaire portal upload so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in the questionnaire portal upload 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.
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 retried the upload immediately under a new attempt each time, so the portal saw multiple copies of the same file and flagged it.

Variant phrasings

questionnaire agent retried portal upload without backoff file flagged as duplicate

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: questionnaire agent retried portal upload without backoff file flagged as duplicate

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

the questionnaire portal upload 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 questionnaire portal upload 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/pstbCemHOcKTQkg5pmcHpvUQ

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

Thread query: questionnaire agent retried portal upload without backoff file flagged as duplicate

TL;DR: Fix this in the questionnaire portal upload by acting on the exact message first: add backoff before any upload retry, name each upload with a key built from the questionnaire ID and file hash, and check the portal file list for that key before uploading again so a retry reuses the first upload. 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.