Run batches
This section is for everyone who works with batches day to day: the people who answer questions, the approvers, and whoever opens the batches. None of it needs a terminal.
Where to look
Section titled “Where to look”| Page | Shows |
|---|---|
| Today | What needs you: the questions in your queues and the changesets waiting for your approval, across every batch. Then what’s running. |
| Batches | Every batch, open and finished, with how far each has got. |
| Questions | Every open question. Mine shows yours; Everyone shows all of them. |
| Motions | Each motion, its live version, and its drafts. |
Open a batch
Section titled “Open a batch”On Batches, choose Open batch:
- Motion: which motion to run.
- Version: the live one, unless you’re trying a draft on real companies.
- Companies: a list from the CRM, or company ids.
- Label: a name people will recognise, such as “week 45” or “rehearsal”.
Motions reads the companies from the CRM and starts at once. Whoever opened it is recorded.
Read the batch screen
Section titled “Read the batch screen”The top of the batch shows its status (running, waiting on people, paused or done), how far it’s got, and its controls: Pause or Resume, Upgrade, and the More actions menu.
Below are five tabs:
- Overview: the steps, in order, with how many companies are at each cell state, and what each barrier is waiting for.
- Companies: the wall, one row per company and one brick per step. Choose a company to open its drawer.
- Questions: this batch’s open questions, grouped by queue.
- Changesets: each changeset, with its operations and state.
- Activity: everything that happened, newest first: runs, answers, approvals, and who did what.
The page updates live. If the connection drops, a badge says so and it catches up when it’s back.
The company drawer
Section titled “The company drawer”The drawer is everything about one company in this batch: its lane and why, each step’s state, the facts each step found, its questions and answers, the operations proposed for it, and each step’s logs and errors. When a step failed, the drawer offers Retry for it.
When it’s finished
Section titled “When it’s finished”A batch is done when every company is done, held or dropped, and every changeset is written or rejected. It stays in Batches with its full record.
Motions is built by Pruma. These docs describe what the platform does today; Limitations lists what it doesn't do yet. Open the app