You have almost certainly scanned that same code already. Reload the page. Otherwise: is the camera actually running, and is the whole code inside the frame?

No. For X1, X2, X3 and BAD-200 amber is the correct result and the step has passed.

Tap Use photo, and add one to the sharpness tally. It ignores badges while it waits, so nothing else will scan until you answer it.

Log it exactly as it appears and scan the same badge again. The capture is safe in the hub meanwhile. A red result is a real finding, not a mistake by you.

No. On these two jobs a scan sends itself. The exception is manual entry with the camera switched off, which is why B5 says the camera must be running.

No, that is correct. Every device mints its own capture id, so each scan is a separate person as far as the system is concerned. Expect roughly fifteen by the end. They are all deleted afterwards and the contact count is checked back to where it started.

Write it in the log in plain words and carry on. An odd thing you cannot explain is the most useful row on the sheet.

The red one is Capture a lead and it writes into our real lead database. Navy keeps every bench record in one place and makes the clean-up afterwards exact.

This is deliberate, so a badge sitting in front of the lens cannot quietly double up. It is also the single thing most likely to make you think the app is broken when it is not. Any step below that repeats the badge starts with a reload.

So the numbered log and the numbered list I read out of FileMaker line up one to one.

A capture that went wrong is the most valuable row on the sheet.

It is waiting for you and it ignores every badge while it waits. That tally is a real result, not an interruption: it decides whether we lower the sharpness bar before the show.