Ask for Approval creates an authorization step. The flow must evaluate the result before performing work that requires approval. Requested, Approved, and Rejected are different outcomes. A record existing in the approval table proves a request was made, not that the approver accepted it.
Test approval and rejection paths separately. A rejected item should not receive a fulfillment task that the policy reserves for approved requests. Also check that an inactive flow has no effects and that the approver identity is appropriate. The simulator pauses at the approval step and resumes later actions only after Approved. It exposes the approval record so you can inspect the target and result. Keep administrative test actions separate from granting the requester the power to approve their own work.