Foundry is available to select customers only, and the Job queue is visible to members with the Foundry Manager role. Contact us to request access.
Job lifecycle
Every job carries a status. As a runner picks up the work and trains the reference object, the status advances:| Status | Meaning |
|---|---|
| Queued | Waiting for an available runner to claim it. |
| In Progress | A runner has claimed the job and is training the reference object. A progress bar shows how far along it is. |
| Done | Training finished and the reference object was uploaded. The source object is now Trackable. |
| Rejected | The request was dismissed before completion. |
| Failed | A processing error occurred. The job can be requeued to try again. |
What each job shows
Selecting a job opens its detail panel, which includes:- The object being trained, with its thumbnail
- The view mode and training mode the request was submitted with
- Any objects to avoid that were selected to reduce false matches
- Live progress and the runner currently handling it, while in progress
Training parameters
These are chosen when tracking is enabled on an object and describe how the object is handled in the real world, which helps produce an accurate reference object: View mode| Mode | Best for |
|---|---|
| Front | Objects viewed only from the front: wall-mounted panels, controls, screens. |
| Upright | Objects that stay upright and are approached from any side: benchtop equipment, freestanding machines. |
| All angles | Objects picked up and rotated freely: handheld parts and tools. Trains longer and carries a higher false-positive risk. |
| Mode | Typical runtime | Best for |
|---|---|---|
| Standard | ~8 hours | Most objects |
| Extended | ~18 hours | Small, handheld objects that need extra detail |
Managing a job
From the queue you can act on jobs that need attention:- Requeue a failed job to try training again.
- Reject a job that’s no longer needed so it stops occupying the queue.
