AppsSynthetic Data

Jobs at scale · Autessa Synthetic Data

Job status, progress and partial results

Autessa Synthetic Data tracks every job with live progress and plain statuses. You see rows generated and rows written against rows requested, every batch, and a plain status. When a job stops short, it says why.

A core synthetic data capability, done properly
Start free
Job statusesSAMPLE

Working (the page keeps polling)

PendingGeneratingAwaiting reviewWriting

Final

CompletedPartially completedFailedCancelledDiscarded
Requested 1,000 but generated 940. Why it stopped short:
  • Two batches in a row produced no valid rows.

The problem

A spinner is not a status

When a generation job ends with fewer rows than requested, or fails, you need to know what happened and what you got. Vague errors leave you guessing whether to retry, append or give up.

What you get

  • Nine statuses: Pending, Generating, Awaiting review, Writing, Completed, Partially completed, Failed, Cancelled and Discarded.
  • Active statuses pulse and the page keeps refreshing; final ones are static.
  • Rows requested, generated and written are counted separately.
  • Partially completed jobs list each reason they stopped short.
  • Failed jobs say how many rows were written before the failure.
  • The home list shows every company job with target, status, rows and when it was created.

How it works

How does job status, progress and partial results work?

  1. Open Synthetic Data

    The home lists every job, newest first, with its target, status and rows.

  2. Open a job

    See its status, target, last update and, while active, a progress bar and batch list.

  3. Read the outcome

    Final states show what was written or generated, any shortfall reasons and the next action.

Every option

Every job status

OptionWhat it does
PendingCreated and waiting to start.
GeneratingBatches are being generated.
Awaiting reviewReview mode: rows are staged for approval or discard.
WritingApproved rows are being written, or the file is being assembled.
CompletedFinished with every requested row.
Partially completedFinished with fewer rows, for example after a storage limit, running out of AI budget or repeated empty batches. Reasons listed.
FailedStopped by an error; rows written before the failure are reported.
CancelledStopped on request after the batch in progress.
DiscardedStaged rows thrown away; nothing more written.

Permissions

Who can do what?

WhoCan
People in your companyCreate datasets, see the company list of jobs, open any job and review, approve, append, cancel or discard it.

Connected

How job status, progress and partial results connects to the rest of Autessa

FAQ

Questions about job status, progress and partial results

Why did my job end partially completed?

Common reasons are reaching the database storage limit, running out of AI budget or credits, or several batches in a row producing no valid rows. The job lists the exact reason.

Can I cancel a job?

Yes. Cancel stops generation after the batch in progress. Rows already written stay written, and a job that has not started is cancelled immediately.

Who can see my jobs?

Jobs belong to your company, so people in your company see them in the Synthetic Data list.

Try job status, progress and partial results in Autessa Synthetic Data

Autessa Synthetic Data tracks every job with live progress, per-batch status and plain statuses, and explains any shortfall in plain words.

Start free

Describe it · review it · write it · or download JSONL and CSV

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