# Background jobs and walkers (admin)

> For administrators: autonomous review jobs, why a job is parked rather than refused, and how to follow the queue.

_Source: E-Sharp (esharp.se) · Probe guide_


*This page is for the administrator.*

Probe can run reviews autonomously in the background. This page describes the queue and the **walkers** that work through it.

## The queue

You can queue a board for an autonomous pass (a *walk* or *rewalk*). Each job has a state in the queue that you can follow.

## Accept-and-park

Admission is **accept-and-park**: a take missing its schematic or BOM is **not refused** — it's accepted and parked immediately with a note on what's missing. That's deliberate; refusing would push the problem back to whoever queued it.

## Walkers and stalled runs

Walkers are the workers that take jobs off the queue. In the fleet view you see which jobs are parked and which runs have stalled, plus cost and shift per board — the basis for keeping the fleet moving.

> To confirm: whether autonomous walkers are offered to customers or only used in E-Sharp's own operations is an open question (see the plan).

---

Related: [monitor the fleet and the server](/en/probe/support/monitor-the-fleet).

*Probe is E-Sharp's design-review engine.*
