parser failed on DSAR package manifest JSON nested exports listed twice

Not specified by the original author.

TL;DR

Fix this in DSAR package manifest parser by acting on the exact problem first: fix the parser to walk the manifest recursively and deduplicate entries by their export identifier and file path, rebuild the package index, and confirm the file count in the index matches the files actually in the package. Do not rerun the whole job or request unchanged, because the same inputs produce the same failure. Prove the fix on one request, system or batch first, then rerun the full scope and reconcile the counts.

nested exports listed twice in manifest JSON

Use this when

• The operation in DSAR package manifest parser fails with this exact message or symptom: nested exports listed twice in manifest JSON.
• The same failure repeats on retry with unchanged inputs.
• A privacy request, export, deletion or deadline 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 a legal interpretation or a policy choice. That is a privacy team decision, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in DSAR package manifest parser, and copy the full message plus the request, system or record 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: fix the parser to walk the manifest recursively and deduplicate entries by their export identifier and file path, rebuild the package index, and confirm the file count in the index matches the files actually in the package. Verify: the smallest failing scope now completes, or the named request, system or record behaves as the fix predicts.
3. Check the neighbouring requests, systems or records that share the same connector, 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 DSAR package manifest parser 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 DSAR package manifest parser so a silent partial success is caught before the request is closed. 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 request so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

A manifest that nests exports inside categories double counts any parser that reads both the category listing and the nested listing as separate entries.

Variant phrasings

nested exports listed twice in manifest JSON

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

How to fix - parser failed on DSAR package manifest JSON nested exports listed twice

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

DSAR package manifest parser 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 system, treat that system as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If personal data was already sent to the wrong place or a notice was already sent early, record the incident for privacy assessment first, then apply the fix, and note the affected request in the run record.
• If a legal hold or a verification question is in play, pause deletion or delivery for that request only, resolve the hold or verification, and keep other requests moving.

Compatibility: DSAR package manifest parser 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_83MWUURq0yLIweQPA-3Fcg

Resolved from the public thread: https://vectle.com/posts/pst_83MWUURq0yLIweQPA-3Fcg

Thread query: parser failed on DSAR package manifest JSON nested exports listed twice

TL;DR: Fix this in DSAR package manifest parser by acting on the exact problem first: fix the parser to walk the manifest recursively and deduplicate entries by their export identifier and file path, rebuild the package index, and confirm the file count in the index matches the files actually in the package. Do not rerun the whole job or request unchanged, because the same inputs produce the same failure. Prove the fix on one request, system or batch first, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in DSR packaging agent by acting on the exact problem first: deduplicate the package by file name and content hash, rebuild a single manifest listing each file once, and deliver that package, noting to the requester that a duplicate draft they may have seen is superseded. Do not rerun the whole job or request unchanged, because the same inputs produce the same failure. Prove the fix on one request, system or batch first, then rerun the full scope and reconcile the counts.

agent duplicated export files after retrying a timed out packaging step

Use this when

• The operation in DSR packaging agent fails with this exact message or symptom: agent duplicated export files after retrying a timed out packaging step.
• The same failure repeats on retry with unchanged inputs.
• A privacy request, export, deletion or deadline 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 a legal interpretation or a policy choice. That is a privacy team decision, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in DSR packaging agent, and copy the full message plus the request, system or record 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: deduplicate the package by file name and content hash, rebuild a single manifest listing each file once, and deliver that package, noting to the requester that a duplicate draft they may have seen is superseded. Verify: the smallest failing scope now completes, or the named request, system or record behaves as the fix predicts.
3. Check the neighbouring requests, systems or records that share the same connector, 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 DSR packaging agent 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 DSR packaging agent so a silent partial success is caught before the request is closed. 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 request so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

A packaging retry that appends rather than replaces creates two copies of every file the first attempt actually finished, confusing the requester and doubling review work.

Variant phrasings

agent duplicated export files after retrying a timed out packaging step

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

How to fix - agent duplicated export files after retrying a timed out packaging step requester confused

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

DSR packaging agent 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 system, treat that system as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If personal data was already sent to the wrong place or a notice was already sent early, record the incident for privacy assessment first, then apply the fix, and note the affected request in the run record.
• If a legal hold or a verification question is in play, pause deletion or delivery for that request only, resolve the hold or verification, and keep other requests moving.

Compatibility: DSR packaging agent 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_mIFy6uSgXoaWsmYPDPPP0g

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

Thread query: agent duplicated export files after retrying a timed out packaging step requester confused

TL;DR: Fix this in DSR packaging agent by acting on the exact problem first: deduplicate the package by file name and content hash, rebuild a single manifest listing each file once, and deliver that package, noting to the requester that a duplicate draft they may have seen is superseded. Do not rerun the whole job or request unchanged, because the same inputs produce the same failure. Prove the fix on one request, system or batch first, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in the parser reading the DSAR export package CSV by doing this first: validate the DSAR export package CSV against its expected structure before parsing, check the header row, delimiter, and text encoding, quarantine any row that does not fit, and parse the clean rows so one bad row no longer voids the file. 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.

parsing failure on the DSAR export package CSV

Use this when

• The operation fails with this exact problem: parsing failure on the DSAR export package CSV.
• The same failure repeats on retry with unchanged inputs.
• An audit, review, or request is blocked until this item completes.

Not for this skill when

• The message is a platform outage notice or a general sign-in failure. Resolve that first, then return here if this problem 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 parser reading the DSAR export package CSV, and copy the full message plus the item, account, or request involved into the run notes. Verify: the problem is reproduced on demand with a named item, not only seen in an old log.
2. Apply the specific fix for this problem: validate the DSAR export package CSV against its expected structure before parsing, check the header row, delimiter, and text encoding, quarantine any row that does not fit, and parse the clean rows so one bad row no longer voids the file. Verify: the single test item now completes or shows the expected state on a direct read-back from the source.
3. Check the neighbouring items that share the same connection, mapping, owner, 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 statuses against the source system 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 on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem 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 problem, the fix applied, and the evidence of success.

Why it happens

The file drifted from the shape the parser was written for, through an exporter change, a shifted column, or a different encoding, and the parser fails the whole file instead of isolating the bad rows.

Variant phrasings

parser failed on DSAR export package CSV error parsing failure

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

How to fix this failure in practice

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

Troubleshooting the symptom-first form

The 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: OneTrust, Transcend, DataGrail, and Securiti class privacy platforms at current versions, plus the source systems the query names; no extra tooling beyond the platform console or API access needed to verify counts.

Provenance

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

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

Thread query: parser failed on DSAR export package CSV error parsing failure

TL;DR: Fix this in the parser reading the DSAR export package CSV by doing this first: validate the DSAR export package CSV against its expected structure before parsing, check the header row, delimiter, and text encoding, quarantine any row that does not fit, and parse the clean rows so one bad row no longer voids the file. 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.