Several recurring defects are configuration, not product. A child region larger than its parent image, often by a rounding error after a fixture move, needs a region inset by a few pixels on each side. Image rotation from the view menu, rather than from the acquisition cell, flips coordinate sense and makes correct math look wrong. A local file path in the header means the job is running from the laptop, not camera memory. Property-sheet edits sever cell links. Filter kernels must be odd, and a reversed min and max silently defeats the tool. Patterns fail on score, angle range, granularity that trained the background, or a timeout longer than the cycle. Edges fail on strength, polarity, and region direction: the search must cross the transition. Blobs fail on threshold, area limits, and boundary handling. Debounce and trigger source explain double fires. These checks are faster than a hardware project and should be exhausted before the job is declared incapable.

Four diagnostic cards ask whether image and ROI are valid, train and run images match, search coverage includes the part, and execution meets its deadline.
D20. These checks separate lost coverage, image mismatch, search limitations and timing from an actual product defect. They are diagnostic questions, not permission to alter approved limits or automatically move the inspection region.
Click the diagram to enlarge it.