Skip to content

Batches

A sweep batch runs one operation many times while varying chosen parameters across rows. Where the Sandbox sweep (x2, x4, x8) rolls new seeds on identical settings, a batch changes the settings themselves: three prompts times two guidance values, one row each. Use it for wedges, lookdev grids, and coverage passes.

The batch list

Open Batches from the mode nav. The list shows every batch with its name, status (draft, running, paused, complete, failed, cancelled), and a done-out-of-total count. Click New sweep batch to start one.

Create a sweep batch

Step 1: pick a pipeline. Choose the operation the whole batch will run.

Step 2: configure the sweep.

  1. Name it in Batch name.
  2. Fill in "Base values (shared by every row)". This is the operation's full form, references included. Everything here is identical across all rows.
  3. In "Sweep axes", tick the parameters you want to vary and enter comma-separated values for each. Each ticked parameter becomes an axis; the batch builds every combination. The live counter keeps you honest: "N rows will be created (3 x 2)."
  4. Click Create N Rows.

Row limit

The row count is capped. If your axes multiply out past the limit, trim some values before creating. Two axes of reasonable size beat four axes of everything.

The batch is created as a draft, so nothing runs yet.

The batch detail view

The header actions are Start, Pause, Cancel remaining rows, and Delete batch. Deleting is safe for your results; as the app puts it, deleting a batch "does not delete any already-generated outputs".

The table (virtualized, so thousands of rows scroll fine) shows the row number, Label, one column per varied parameter, Status, and Output. While the batch is a draft or paused, cells are editable, so you can hand-tune individual rows: fix a typo in one prompt, nudge one value, without rebuilding the batch.

Row statuses: pending, queued, running, complete, failed, cancelled, skipped.

The inspector rail on the right summarizes the Pipeline, Progress, Concurrency (how many rows run at once), the Sweep axes, and the Base values.

Run it

  1. Click Start. Rows queue up and run as jobs.
  2. Watch progress in the table, or from anywhere via the "N batches running" link on the bottom panel.
  3. Pause any time; edit cells; resume.
  4. When rows finish, click a row's View to select its output in Sandbox, where the Inspector shows the exact recorded settings.

Failed rows don't stop the batch; the rest keep going. Review failures afterward and rerun what matters.

Reviewing a finished batch

The Output column is your contact sheet. Step through View on each row, then promote the winners: right-click the asset in Sandbox and add it to a Kitly Asset, or use it as a source for the next operation. The varied-parameter columns tell you exactly which combination produced which result, which is the whole point of a wedge.