Follow batch progress and execution results
Find a batch, inspect per-device approvals and output, and distinguish cancellation from a tenant-wide delivery stop.
Before you start
- Dispatch a task or select an existing batch in the active organization.
- For approvals, use an eligible administrator and current MFA verification.
Screenshots show the Rapport interface with example data. Use your organization’s devices and values. Select an image to view it at full size.
Choose the type of activity
Open Activity. Use Batches for task groups, Approvals for pending command jobs, Terminal sessions for remote-session records, and File transfers for transfer records. New batch starts a new Run a task flow.
What you should see: You are viewing the correct operational record rather than a similar-looking activity category.
Open the batch and read its progress
Open a batch to see its name, command type, device count, and creation time. Review Progress and its Succeeded, Failed, Cancelled, Awaiting approval, and In flight counts. A finished batch can contain mixed outcomes.
What you should see: The top-level status is grounded in separate device outcomes.
Inspect the per-device result
In Per-endpoint status, open the expand control for a device. Review stdout and stderr, exit code, duration, truncation indicators, and queued/dispatched/completed times. Follow the device link when the result needs a fresh health, patch, or software observation.
Resolve approvals at device scope
Read the approval label on each job. Where you are eligible, use Approve or Reject for that specific request, or follow the Approvals link for the full context and any owner break-glass path. Your own request cannot normally be approved by you.
What you should see: Approved jobs can proceed independently of requests that are still waiting or rejected.
Use cancellation or delivery controls for the right scope
Choose Cancel in-flight when you intend to cancel active jobs in this batch. Emergency stop asks to pause delivery for the entire tenant and cancel every queued or running command. Read that confirmation carefully. Once paused, Resume tenant delivery permits delivery again. Read the returned stopped/cancellation-requested count before assuming agents stopped.
| Field or control | What to do |
|---|---|
| Cancel in-flight | Targets the active jobs in the batch. A running job may first show cancellation requested. |
| Emergency stop | Pauses tenant-wide command delivery and cancels or requests cancellation of queued and running commands beyond this batch. |
| Resume tenant delivery | Allows queued, approved commands to be delivered again. It does not recreate cancelled jobs or undo completed work. |
Confirm the operational outcome
After the final job results arrive, compare them with the original goal. Open the device’s relevant tab to verify the new state. For file transfers, inspect the transfer result and download availability; for terminal work, inspect session metadata rather than expecting a recording of terminal content.
What you should see: You can report which devices completed, failed, or remain blocked, with the recorded evidence for each.
If something doesn’t work
A batch cannot be found.
Confirm the active organization and open the batch from its Activity list. The batch may belong to a different tenant.
A batch is waiting even after one approval.
Review every per-device job. Decisions are separate, and offline agents may still be waiting to receive approved work.
Output is shorter than expected.
Check the truncation badge and stdout/stderr fields. A truncated record is not the full output; avoid treating the visible excerpt as complete.