A Preflight Popup Stopped the Queue: Define an Operator Handoff
Treat a preflight popup as a required operator decision, not an obstacle to bypass. Record what triggered it, which file state was inspected, and whether a supervised proof is required before the queue restarts.
A stopped queue may be doing useful work
Demand evidence comes from a 2026 LightBurn thread: a 2026 LightBurn user reports duplicate-checking popups interrupting a server-driven file-loading workflow.
Record the popup disposition
- Keep an operator present for validation and machine operation; never disable a check merely to preserve automation.
- Save a screenshot and identify the exact source file and revision.
- Resolve geometry or resource issues in a new controlled version, then run slow preview and supervised proof.
- Restart only after material, fixture, focus, exhaust, work area, and file state are rechecked.
Define the attended validation window
| Popup state | Operator evidence | Disposition |
|---|---|---|
| duplicate warning | selected paths and preview | clean file or documented exception |
| missing resource | font/image/package state | restore before release |
| unexpected size | bounding box and units | return to source |
| unclear message | screenshot and support record | hold queue |
Restart only from one approved file state
A duplicate warning appears after a large SVG loads. The operator records the selected objects, moves them aside for inspection, saves a cleaned revision, and invalidates the old release. Clicking through without understanding leaves two file states competing.
If the popup selects overlapping geometry, follow the duplicate-path release check. After validation, the production-width raster proof tests whether a tiny cell represents the real fill.
X1S Pro automation boundaries
X1S Pro production positioning does not authorize bypassing validation or unattended output. A named operator owns the popup disposition, physical checks, supervised proof, and controlled restart. Treat the X1S Pro production positioning as machine context, not permission to bypass an attended validation stop.
Preflight-handoff questions
Can I disable duplicate checking?
This workflow does not recommend disabling validation. Resolve or document the file condition.
Does a cleared popup make the job safe?
No. It is only file-state evidence; supervised machine and material checks remain.
Who should restart the queue?
A named operator who can verify the disposition and current physical setup.