Batches

A batch is a group of runs spawned in one call. trigger.dev tracks the batch as a parent record so you can monitor and cancel the whole group as one.

Platos uses trigger.dev as the durable execution engine. Batches are a trigger.dev concept that Platos surfaces in the dashboard for visibility. The triggering call (tasks.batchTrigger) and the per-run semantics are unchanged from upstream.

In Platos

The Batches page at /orgs/{org}/projects/{project}/env/{env}/batches lists every batch with its size, the per-status counts, and a progress bar. Click into a batch to see every run in the group.

The most common Platos use of batches is the agent_batch meta-tool. An agent calls agent_batch({ items: [...], prompt: "...per item..." }); the runtime turns each item into one run inside a single batch using agent-batch.task.ts. The agent gets one batch id back; the dashboard shows it as one row with progress.

Cancelling a batch cancels every running and queued run inside it. Completed runs stay completed. Cancellation cascades to tool calls each run had in flight.

Reference

The full reference for batch triggers lives in the trigger.dev docs:

trigger.dev/docs/v3/triggering

Runs: each batch contains many runs.
Platos tasks: agent_batch is the agent-level meta-tool.