Review before write · Autessa Synthetic Data
Exclude rows and regenerate batches
While reviewing, Autessa Synthetic Data lets you exclude single rows and regenerate a whole batch. Excluded rows are never written, and a regenerated batch is replaced with fresh rows before you approve.
The problem
One bad row should not cost you the whole set
Most of a batch is often fine, with a few rows that miss the tone or contain something you do not want in a demo. Sometimes a whole batch went the wrong way. You need to fix both cases without starting the job again.
What you get
- Open a row and press "Exclude row"; it is struck through and never written.
- The page footer counts the rows excluded in the current batch.
- "Regenerate batch" replaces the current batch with freshly generated rows.
- Regenerated batches go through the same validation and de-duplication.
- The job returns to Generating, then back to Awaiting review.
- On the CLI,
exclude-rowstakes zero-based positions within one batch.
How it works
How does exclude rows and regenerate batches work?
Spot a miss
Click the row in the preview grid to open it.
Exclude it
Press "Exclude row". The row is dimmed and struck through.
Or regenerate the batch
If the whole batch is off, press "Regenerate batch".
Keep reviewing
Move to the next batch, then approve when you are happy.
Every option
Exclude and regenerate
| Option | What it does |
|---|---|
| Exclude row | Drops one row from a staged batch so it is never written. |
| Exclude on the CLI | --jobId, --batchId and --rowIndexes (zero-based positions within that batch). |
| Positions shift | After an exclusion, preview the batch again before excluding more. |
| Regenerate batch | Replaces one staged batch; only while the job is Awaiting review. |
| Regenerate on the CLI | --jobId and --batchId. |
Permissions
Who can do what?
| Who | Can |
|---|---|
| People in your company | Create datasets, see the company list of jobs, open any job and review, approve, append, cancel or discard it. |
Where AI does the work
How the generator handles this
A regenerated batch is a fresh model call with the same description, examples and variety ledger, so the replacement rows differ from the ones you rejected.
Generation runs on your company default model, and every row is checked against your columns before it is staged or written.
Your model and PII stripping →Connected
How exclude rows and regenerate batches connects to the rest of Autessa
FAQ
Questions about exclude rows and regenerate batches
Can I undo an exclusion?
Excluded rows are removed from the staged batch. If you change your mind, regenerate the batch or append more rows.
How do I fix a row during review?
Exclude it and regenerate the batch, or approve and edit the row in the table afterwards.
Does regenerating keep my exclusions in other batches?
Yes. Regenerating replaces one batch; the other batches and their exclusions are untouched.
100% customizable, code and all
Make Autessa Synthetic Data fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours