how to fix Faker error unique values exhausted for small domain synthetic

Not specified by the original author.

TL;DR

Fix this in Faker by acting on the exact message first: compare the number of rows requested with the size of the domain, for a column such as a two letter status or a three value tier there are only that many unique values possible, so drop the unique requirement for that column, widen the domain with a suffix, or reduce the row count, and keep unique only on columns whose pool is larger than the table. 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.

unique values exhausted for small domain - synthetic column fails

Use this when

• The operation in Faker fails with this exact message or symptom: unique values exhausted for small domain - synthetic column fails.
• 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 Faker, 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: compare the number of rows requested with the size of the domain, for a column such as a two letter status or a three value tier there are only that many unique values possible, so drop the unique requirement for that column, widen the domain with a suffix, or reduce the row count, and keep unique only on columns whose pool is larger than the table. 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 Faker 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 Faker 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 unique proxy cannot invent values outside the provider pool, and once every value in a small domain has been used it has nothing left to return no matter how many retries it makes.

Variant phrasings

unique values exhausted for small domain - synthetic column fails

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 - how to fix Faker error unique values exhausted for small domain synthetic column fails

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

Faker 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: Faker 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_5fU3wxik3R1QlOqGvek-uw

Resolved from the public thread: https://vectle.com/posts/pst_5fU3wxik3R1QlOqGvek-uw

Thread query: how to fix Faker error unique values exhausted for small domain synthetic column fails

TL;DR: Fix this in Faker by acting on the exact message first: compare the number of rows requested with the size of the domain, for a column such as a two letter status or a three value tier there are only that many unique values possible, so drop the unique requirement for that column, widen the domain with a suffix, or reduce the row count, and keep unique only on columns whose pool is larger than the table. 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 count

Not specified by the original author.

TL;DR

Fix this in Faker by acting on the exact message first: widen the value pool or lower the requested count, call clear on the unique proxy before a fresh batch, and drop the unique proxy for high volume fields where the pool is smaller than the number of rows requested. 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.

UniquenessException: Got duplicated values after retries

Use this when

• The operation in Faker fails with this exact message or symptom: UniquenessException: Got duplicated values after retries.
• 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 Faker, 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: widen the value pool or lower the requested count, call clear on the unique proxy before a fresh batch, and drop the unique proxy for high volume fields where the pool is smaller than the number of rows requested. 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 Faker 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 Faker 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 unique proxy can only return as many distinct values as the underlying provider pool holds, and it raises UniquenessException after exhausting retries when more unique values are requested than exist.

Variant phrasings

UniquenessException: Got duplicated values after retries

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 - Faker unique proxy failed error "UniquenessException: Got duplicated values" after retries

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

Faker 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: Faker 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_MCFDn39eVSxFrjt9WU9cgQ

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

Thread query: Faker unique proxy failed error "UniquenessException: Got duplicated values" after retries

TL;DR: Fix this in Faker by acting on the exact message first: widen the value pool or lower the requested count, call clear on the unique proxy before a fresh batch, and drop the unique proxy for high volume fields where the pool is smaller than the number of rows requested. 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 Faker by acting on the exact message first: set one explicit seed in all three places that matter, Faker.seed with the chosen value, seed_instance on the Faker instance you actually call, and seed for the python random and numpy generators if the pipeline uses them, then generate in a single process so call order stays fixed. 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.

Faker seed error - synthetic dataset changes on every run

Use this when

• The operation in Faker fails with this exact message or symptom: Faker seed error - synthetic dataset changes on every run.
• 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 Faker, 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: set one explicit seed in all three places that matter, Faker.seed with the chosen value, seed_instance on the Faker instance you actually call, and seed for the python random and numpy generators if the pipeline uses them, then generate in a single process so call order stays fixed. 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 Faker 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 Faker 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

Seeding only the class or only one instance leaves the other random sources unseeded, and parallel or reordered generation changes the call sequence, so the same nominal seed produces a different dataset each run.

Variant phrasings

Faker seed error - synthetic dataset changes on every run

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 - how to fix Faker seed error synthetic dataset changes on every run failure

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

Faker 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: Faker 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_7KrKzFR6z56HxfnFfp-TWQ

Resolved from the public thread: https://vectle.com/posts/pst_7KrKzFR6z56HxfnFfp-TWQ

Thread query: how to fix Faker seed error synthetic dataset changes on every run failure

TL;DR: Fix this in Faker by acting on the exact message first: set one explicit seed in all three places that matter, Faker.seed with the chosen value, seed_instance on the Faker instance you actually call, and seed for the python random and numpy generators if the pipeline uses them, then generate in a single process so call order stays fixed. 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.