2. Compare against a clean selection

Goal: Use a clean control without confusing it with a repair.

Before you start: The first review and ConsumersValid.

The idea you will use

Changing the selection changes the reviewed scope. A clean result for another table does not fix Consumers.

Predict before running

What happens if you return to Consumers with its profile?

Build and check

Use the control table to confirm that the previous findings came from the relationships in Consumers.

1. Select Targets and ConsumersValid in the Content Browser, then click Use selected DataTables.
2. In Rules → References and game rules, load Fixtures/bundled-valid.json. This file points to /Game/RowTetherExample/ConsumersValid.ConsumersValid.
3. Wait for the profile-triggered review to finish, then check status and coverage.

Expected result: the run is Completed and has no current reference errors. Empty handles remain optional. You did not need to edit or repair Consumers to get a clean control.

If C4 or C5 still appears, check that you replaced the selection with Targets and ConsumersValid, and that the panel uses bundled-valid.json, not the profile for Consumers.

Check your reasoning

See the explanation

C4 and C5 reappear because the original data has not changed.

Your turn: Return to Targets and Consumers with nullable-handles, check the prediction, then return to the clean control.

Ready to continue when: you can explain which selection and profile support a result.