Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.firstresonance.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

A run batch is a group of runs that share steps. When you sign off, redline, or change the state of a step in one run, ION applies the same change to every other run in the batch that has the matching (“sibling”) step. Run batches are how operators handle build-many-of-the-same-thing workflows without repeating identical actions on every run individually. Batches are most useful when:
  • The same procedure is being executed across multiple parts at once (e.g. a build of 12 boards through the same steps).
  • A redline or process change discovered on one run should immediately apply to every in-flight sibling.
  • A team wants a single “view” of progress across all runs sharing a procedure.

​
Run batches vs individual runs

AspectIndividual runRun batch
Scope of a sign-offThe single runAll sibling steps in the batch
RedlinesRun-localPropagate to all batched siblings
State changes (skip, fail, complete)Run-localPropagate to siblings
Use whenEach unit’s path diverges meaningfullyUnits march through identical steps
Within a batch, only sibling steps propagate. A step that exists in one run but not another won’t be affected by a change to the unique-side run.

​
Prerequisites

  • The runs you want to batch must follow procedures whose step structure matches enough to have shared (“sibling”) steps. Two runs of the same procedure version are the canonical case.
  • Permission to modify run batch membership.

​
Open the Run Batch modal

Open the Run Batch modal from inside a run. The modal shows the current batch (or, if the run isn’t yet in a batch, prompts you to create a new one). Once open, you’ll see:
  • Batch title — editable header at the top.
  • Affected runs only toggle — narrows the list to runs whose sibling step matches the step you opened the modal from.
  • Search — filter the runs list by run ID or run title.
  • Add a Run to the Batch dropdown — multi-select picker for runs not yet in the batch.
  • Unbatch all — footer action to remove every run from the batch.

​
Steps

​
Create a new batch

If you open the Run Batch modal from a run that isn’t yet batched, ION shows the New Batch flow:
  1. Confirm the run you’re starting from.
  2. Give the batch a title (optional but recommended — it shows up in the run list).
  3. Submit. The current run is now Run #1 in the new batch.

​
Add runs to a batch

  1. With the Run Batch modal open on an existing batch, click Add a Run to the Batch.
  2. Search by run ID or title in the dropdown. Runs already in this batch are excluded.
  3. Multi-select the runs you want to add, then click Add N to Batch in the dropdown footer.
After ION updates the batch, those runs immediately participate in propagation for any future changes on shared steps.

​
Set or rename the batch title

Click the title at the top of the modal to enter edit mode. Type the new title, then Submit. Cancelling reverts to the previous title.

​
Remove a run from a batch

In the runs list, expand the run card and click Remove on the run you want out. ION updates the batch and the run continues independently from that point forward — it keeps any sign-offs and redlines it accumulated while batched.

​
Unbatch every run

Click Unbatch all in the modal footer. ION asks you to confirm before clearing the batch. After confirming, every run leaves the batch and continues independently. The batch itself is dissolved.

​
Batch propagation

When you change a step inside a run that belongs to a batch, ION looks at every other run in the batch and finds sibling steps — steps in those runs that match the same step in the batched procedure. The change propagates to every sibling found:
  • Sign-offs — completing or signing a step propagates the same completion to every sibling step.
  • Redlines — changes to step content (added notes, modified instructions, attached images) propagate so every sibling reflects the latest state.
  • State changes — skipping, failing, or reopening a step propagates to siblings.
The Run Batch modal’s “X out of Y runs in batch affected by this step” counter at the top of the runs list shows exactly how many sibling steps will move when you act on the current step. If a step is unique to the current run (no siblings), only the current run will change.

​
Affected runs only

Toggle Affected runs only to hide runs that don’t have a sibling step matching the step you opened the modal from. Useful when a batch has runs at different procedure versions and you want to focus on the subset that this step actually applies to.

​
Tips

  • Search before adding — the Add Run dropdown is paginated; use the search field to narrow results to specific run IDs or titles when the batch is large.
  • Title batches by intent — “PCBA Lot 12” or “Q3 EVT build” reads better than the auto-generated batch ID when scanning the run list later.
  • Unbatch is reversible — a removed run can be re-added to the same batch (or any other batch) at any time. Sign-offs and redlines accrued during membership stay on each run.
  • Redlines mid-batch propagate forward and to in-flight siblings, but historical sign-offs aren’t rewritten. Plan redlines before operators are deep into a batch when possible.