Flow Look Up Records Returns Incorrect RITMIssue A flow populates a reference variable with an incorrect request because its Look Up Records action returns the wrong requested item. Symptoms A variable on the original RITM contains an incorrect REQ value.The Look Up Records action returns multiple RITMs when only one is expected.After modifying the query, the action may return no records.The subsequent Update Record action uses data from an incorrect RITM. Facts The lookup query contained an OR condition that allowed multiple RITMs to match.Testing the original encoded query returned two RITMs instead of the single expected record.Changing the condition before the requested-item variable from OR to AND limited the query to the expected RITM.The no-result behavior was associated with selecting the wrong one of two similarly named catalog variables.A lookup cannot return a RITM that is created after the lookup action has completed. Release Not release specific. Cause The Look Up Records query was too broad because an OR condition allowed records to match without satisfying the requested-item variable condition. This caused multiple RITMs to be returned and an incorrect record to be used by the next flow action. When the query was narrowed, the flow initially returned no records because the query referenced a similarly named catalog variable that was not present on the expected RITM. Resolution Update the Look Up Records conditions so the requested-item variable condition is joined using AND rather than the broader OR condition.Confirm that the variable selected in the lookup condition is the variable present on the expected RITM.Run the corrected query independently and verify that it returns only the expected RITM.Test the flow end to end and confirm that the subsequent Update Record action populates the correct REQ value.If the lookup still returns no records, verify that the expected RITM exists before the lookup action executes.