synthetic dataset failed error k-anonymity check breaks on quasi identif

Not specified by the original author.

TL;DR

Fix this in synthetic data generator by acting on the exact message first: generalise the quasi identifier columns until every combination group reaches k, turning exact age into age ranges and truncating postal codes, then suppress the small remainder groups instead of releasing them. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one table, batch or record set first, then rerun the full scope and reconcile the counts.

k-anonymity check breaks on quasi identifier column

Use this when

• The operation in synthetic data generator fails with this exact message or symptom: k-anonymity check breaks on quasi identifier column.
• The same failure repeats on retry with unchanged inputs.
• Generation, validation or export 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 error remains.
• The operation completes and you only disagree with its output quality. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in synthetic data generator, and copy the full message plus the table, column or job involved into the run notes. Verify: the error is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this error: generalise the quasi identifier columns until every combination group reaches k, turning exact age into age ranges and truncating postal codes, then suppress the small remainder groups instead of releasing them. Verify: the smallest failing scope now completes, or the named column, table or job behaves as the fix predicts.
3. Check the neighbouring tables, columns or jobs that share the same config, schema 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 synthetic data generator 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, distributions or status against the source in synthetic data generator 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

K-anonymity fails when some combination of quasi identifier values forms a group smaller than k, which almost always happens with exact ages, full postal codes or rare job titles left ungeneralised.

Variant phrasings

k-anonymity check breaks on quasi identifier column

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

How to fix - synthetic dataset failed error k-anonymity check breaks on quasi identifier column

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

synthetic data generator 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: synthetic data generator at current versions, plus the platform API or console 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/pstq06arbhC80YM76yJlvdDA

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

Thread query: synthetic dataset failed error k-anonymity check breaks on quasi identifier column

TL;DR: Fix this in synthetic data generator by acting on the exact message first: generalise the quasi identifier columns until every combination group reaches k, turning exact age into age ranges and truncating postal codes, then suppress the small remainder groups instead of releasing them. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one table, batch or record set first, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in synthetic data privacy check by acting on the exact message first: filter the synthetic output by distance to the nearest real row, drop or regenerate every synthetic record that falls inside your minimum distance threshold, and generalise quasi identifier fields such as age and admission dates before the next check. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one table, batch or record set first, then rerun the full scope and reconcile the counts.

record too similar to real patient row

Use this when

• The operation in synthetic data privacy check fails with this exact message or symptom: record too similar to real patient row.
• The same failure repeats on retry with unchanged inputs.
• Generation, validation or export 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 error remains.
• The operation completes and you only disagree with its output quality. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in synthetic data privacy check, and copy the full message plus the table, column or job involved into the run notes. Verify: the error is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this error: filter the synthetic output by distance to the nearest real row, drop or regenerate every synthetic record that falls inside your minimum distance threshold, and generalise quasi identifier fields such as age and admission dates before the next check. Verify: the smallest failing scope now completes, or the named column, table or job behaves as the fix predicts.
3. Check the neighbouring tables, columns or jobs that share the same config, schema 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 synthetic data privacy check 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, distributions or status against the source in synthetic data privacy check 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 synthesizer trained on a small or skewed cohort can reproduce near copies of real rows, and the privacy check flags any synthetic record whose distance to a real record is too small.

Variant phrasings

record too similar to real patient row

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

How to fix - synthetic data privacy check failed error record too similar to real patient row

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

synthetic data privacy check 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: synthetic data privacy check at current versions, plus the platform API or console 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_Wpdv2Oq2WXcRdUVlyP5tYQ

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

Thread query: synthetic data privacy check failed error record too similar to real patient row

TL;DR: Fix this in synthetic data privacy check by acting on the exact message first: filter the synthetic output by distance to the nearest real row, drop or regenerate every synthetic record that falls inside your minimum distance threshold, and generalise quasi identifier fields such as age and admission dates before the next check. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one table, batch or record set first, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in synthetic data agent workflow by acting on the exact message first: run the privacy checks one at a time in a fixed order, distance check, k anonymity, then inference tests, saving each result before starting the next so a late failure never erases earlier evidence. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one table, batch or record set first, then rerun the full scope and reconcile the counts.

agent failed to complete - validate synthetic data privacy

Use this when

• The operation in synthetic data agent workflow fails with this exact message or symptom: agent failed to complete - validate synthetic data privacy.
• The same failure repeats on retry with unchanged inputs.
• Generation, validation or export 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 error remains.
• The operation completes and you only disagree with its output quality. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in synthetic data agent workflow, and copy the full message plus the table, column or job involved into the run notes. Verify: the error is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this error: run the privacy checks one at a time in a fixed order, distance check, k anonymity, then inference tests, saving each result before starting the next so a late failure never erases earlier evidence. Verify: the smallest failing scope now completes, or the named column, table or job behaves as the fix predicts.
3. Check the neighbouring tables, columns or jobs that share the same config, schema 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 synthetic data agent workflow 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, distributions or status against the source in synthetic data agent workflow 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

Stacking every privacy metric into one step means the slowest or most fragile check fails the whole validation and discards the results that already completed.

Variant phrasings

agent failed to complete - validate synthetic data privacy

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

How to fix - agent failed to complete validate synthetic data privacy error failure

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

synthetic data agent workflow 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: synthetic data agent workflow at current versions, plus the platform API or console 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_xxJxttv62vosn8O9G3efeg

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

Thread query: agent failed to complete validate synthetic data privacy error failure

TL;DR: Fix this in synthetic data agent workflow by acting on the exact message first: run the privacy checks one at a time in a fixed order, distance check, k anonymity, then inference tests, saving each result before starting the next so a late failure never erases earlier evidence. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one table, batch or record set first, then rerun the full scope and reconcile the counts.