Trigger modes
| Trigger | Typical use | Data available |
|---|---|---|
manual_enter | Bench testing or controlled manual operation | Empty trigger payload |
scanner_input | Production or traceable operator flow | Usually includes serial number |
python_event | Hardware-driven automation | Plugin-defined event payload |
Routing snapshots
When a trigger fires, Corvus captures the active routing selection as a snapshot. That snapshot contains
values such as entry_id, part_number, part_name, and revision. Plugin logic can branch on those
values, but the snapshot stays fixed for the run.
{
"entry_id": "AMP-100_full-test",
"part_number": "AMP-100",
"part_name": "Digital Audio Amplifier v1.0",
"description": "Rev A — Full Test",
"revision": "Rev A"
}
Job behavior and operator expectations
Corvus controls the job lifecycle. The scheduler assigns work to available job slots and advances states internally.
Prompt handling matters. Sequences may include user prompts that block progress until an operator action is recorded.
Abort, fail, and error are different. A value outside spec is a fail, not a hardware error.
Result review
The Result Viewer is the primary place to inspect completed runs. Operators and engineers can search by serial number, part number, sequence name, or report ID, then open the full report to inspect step-level outcomes and raw measurement details.
- PASS means validations completed successfully.
- FAIL means the run completed but one or more validations were out of spec.
- ERROR means execution failed due to a runtime problem.
- ABORTED means the run was intentionally interrupted.