An approval response contains an outcome such as Approve or Reject. Compare the documented outcome text exactly and put the corresponding work in the correct branch. Sending a reimbursement instruction after the Condition, outside both branches, can authorize work even when the approver rejected it.
The rejected path still needs a useful result. Tell the requester that the decision was rejected, update the tracking record, or return it for correction according to the task. A timeout is another state and needs its own policy; it is not a synonym for Approve. These exercises run both explicit outcomes and ask you to inspect which connector effects occurred. The goal is a clear relationship between the human decision and the downstream action, with enough context in the notification to identify the request.