Render Batch
The Render Batch button walks a row range from start to end and renders every row in it. Use it when you know exactly which rows to render right now; use Agent Mode when rows should render as new data comes in, or as a 24/7 render bot.
Running a batch
Section titled “Running a batch”- Connect a data source and set Output Path. Render Batch reads from the first connected file, worksheet or view.
- Enter the range in the Start and End boxes under Data Preview (both inclusive). See Row numbering for where data starts in each source.
- Pick Render Settings and Output Module templates (or drive them per row via columns, see Render Settings).
- Click Render Batch.

The status bar shows the current row, rows done out of the total, and an estimate of the time remaining. The estimate appears once the first row has finished and adjusts as the batch goes on.
Save your project first
Section titled “Save your project first”Render Batch, Agent Mode and row preview all refuse to start until the project has been saved at least once. With Render from a temporary copy on, save your latest changes too, or they are lost after the first row.
Behavior details
Section titled “Behavior details”- Empty rows are skipped. An empty row between rows of data is counted as skipped and the batch continues.
- The batch ends with your data. When the range reaches past the last
row of data, the batch stops there and says so (“The data ends before
row 52.”). An End row larger than your data, such as
9999for “all of it”, is fine. A row you add below your data while the batch runs is rendered if it is there by the time the batch gets to it, except in Airtable, where a record added mid-batch waits for the next batch. - Errors do not stop the batch. A row that fails to inject or render is counted as failed and the batch moves on. The summary at the end reports rendered / skipped / failed counts. The one exception: when your Google or Airtable sign-in stops working, the batch stops, because no later row could be read either. The status bar says so and asks you to sign in again.
- Stopping: Stop Batch takes effect between rows. The row that is rendering always finishes first.
- Edits during a batch are used. Each row is read when the batch reaches it, so you can fix a row that has not rendered yet without restarting.
- Airtable row numbers stay fixed. Each row number keeps pointing at the record it meant when the batch started, even if the view’s filter or sort changes during the batch. A record added meanwhile waits for the next batch; a deleted one fails its row.
- Render Batch does not write to the
statuscolumn; that is Agent Mode’s job. It can fill in delivery information columns.