Most likely issue — Step 6 is outside the If block and may be overwriting your changes. In Image 3, step 6 ("Update Requested Item Record") sits outside the If condition at step 4. This means it executes regardless of whether the If condition is true or false. If step 6 doesn't set Approval to "Approved," it could be resetting or leaving the RITM unchanged — or worse, overwriting what step 5 just did. Check what fields step 6 is setting.
Second suspect — the If condition at step 4 may be failing silently. Your Condition 2 checks that the RITM's Approval field is Not Yet Requested. By the time the flow reaches this step, the RITM approval value may have already shifted to Requested (if an approval rule or business rule kicked in on the RITM when the REQ was submitted). If that's the case, the entire If block (including your Update at step 5) is being skipped. To verify this, add a Log action before the If and after it (or inside the Else branch) to confirm whether the condition is evaluating to true.
Third thing to check — the Lookup at step 3. Make sure it's actually returning a record. If the Lookup doesn't find a matching RITM, the Update Record in step 5 would silently do nothing. Confirm the lookup conditions (it should be querying sc_req_item where request = trigger record or similar).
Recommended fixes:
-
Remove or review step 6 — if it's not needed, delete it. If it is needed, make sure it isn't conflicting with step 5.
-
Relax the If condition — instead of checking Approval is Not Yet Requested, consider changing Condition 2 to Approval is not Approved (using "is not" operator). This covers all non-approved states rather than just one specific state.
-
Add debug logging — drop a Log step right after step 3 that outputs the RITM sys_id and current approval value from the Lookup result. This will tell you immediately whether the lookup is working and what state the RITM is actually in when the flow evaluates it.
-
Check for competing logic — look at any Business Rules on sc_req_item that fire on update and might be reverting the Approval field, and also check if there's a separate RITM-level approval flow that's conflicting.
