duplicate tasks created for same image after failed import retry error

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.

Not specified by the original author.

TL;DR

Fix this in Document360 by acting on the exact symptom first: dedupe imported images by file hash before inserting them, point each article embed at the surviving image copy, and delete the duplicate copies only after every article renders its screenshots again. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Document360 drive import duplicates images and breaks embedded screenshots in articles

Use this when

• Work in Document360 shows this exact symptom: Document360 drive import duplicates images and breaks embedded screenshots in articles.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Document360, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: dedupe imported images by file hash before inserting them, point each article embed at the surviving image copy, and delete the duplicate copies only after every article renders its screenshots again. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Document360 that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Document360 drive import duplicates images and breaks embedded screenshots in articles

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - Document360 drive import duplicates images breaking embedded screenshots in articles

The how to phrasing for the same problem in Document360. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Document360 troubleshooting for this symptom

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

Why it happens

Each import created fresh image records instead of matching existing files, so embeds pointed at copies that were later cleaned up and the screenshots broke.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Document360 at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

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

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

Thread query: Document360 drive import duplicates images breaking embedded screenshots in articles

TL;DR: Fix this in Document360 by acting on the exact symptom first: dedupe imported images by file hash before inserting them, point each article embed at the surviving image copy, and delete the duplicate copies only after every article renders its screenshots again. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Not specified by the original author.

TL;DR

Treat every timeout as unknown and verify before retrying: after a timed-out create, look the candidate up by email before re-posting. A timeout means the response was lost, not that the write failed, so blind retries create duplicates. Merge the existing dupes on email, then make the import idempotent with check-before-create plus a client-generated idempotency key.

The error

Bulk import finished with 300 extra candidates - the retry loop re-POSTed creates that timed out, but the first writes had already succeeded

Steps

1. Pause the import loop so no more duplicates are created. Expected: the candidate count stops growing.

2. Find the duplicates: query the ATS for candidates sharing the same email address. Expected: groups of 2+ records with identical emails, created minutes apart.

3. Merge each group into one record, keeping the richest profile and all attached notes and activities. Expected: one candidate per email, with no notes or history lost.

4. Change the retry logic: on timeout, look the candidate up by email first and only create when the lookup finds nothing. Expected: re-running a timed-out batch creates zero new records.

5. Attach a client-generated idempotency key (a stable value per candidate, e.g. derived from the source row) to every create call so a repeated request is deduplicated server-side. Expected: the ATS returns the existing record instead of creating a second one on a duplicate key.

6. Set sane timeouts and log every retry decision with its verification result. Expected: future timeouts are audited as verified-absent-and-reposted or verified-present-and-skipped.

Use this when

• A bulk import or sync creates candidates via POST with retry logic
• Duplicates appear after slow, flaky, or timed-out runs
• An agent syncs candidates from a spreadsheet, CSV, or external system

Not for this skill when

• Duplicates come from two source systems with genuinely different emails (that is a matching problem, not a retry problem)
• The source data itself has dupes (dedupe the source before importing)
• Records were intentionally created twice, e.g. separate applications per job (check your dedup policy first)

Variant phrasings

• retry loop created duplicate candidates after POST timeout
• bulk import double-created candidates on a slow API
• timeout but the write succeeded, duplicate ATS records
• import agent re-submitted candidates that were already created

Why it happens

An HTTP timeout only means the client never saw the response; the server may have completed the write. The retry loop assumed timeout equals failure and re-posted unconditionally, so every timed-out create ran twice. Without a check-before-create or an idempotency key, nothing stops the second write.

Edge cases

• Server 500s that partially wrote: same rule, verify before retrying on any ambiguous response.
• Email missing or malformed in the source row: fall back to an external source ID for the lookup key.
• Concurrent imports: two workers can both pass the check, so the idempotency key is the real guard.
• Merge order matters: keep the record with the most complete history as the survivor.

Provenance

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

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

Thread query: bulk-import agent created 300 duplicate candidates - the retry loop on a timed-out POST never checked that the first write had succeeded

TL;DR: Treat every timeout as unknown and verify before retrying: after a timed-out create, look the candidate up by email before re-posting. A timeout means the response was lost, not that the write failed, so blind retries create duplicates. Merge the existing dupes on email, then make the import idempotent with check-before-create plus a client-generated idempotency key.