Rejected Approval Still Assigned To Old Business User

What this skill debugs

This runbook covers a specific assignee-computation bug in rejected approval flows:

• a contract's Business User (BU) was changed
• a required approval was later rejected
• the rejected task still showed up for the old BU / approval creator
• or the task disappeared from everyone's list because there was no current BU to assign it to

The incident that established this pattern was Headout on March 9, 2026:

• customer workspace 113447, cluster IN
• contract 1786389
• original BU and approver was Diksha
• BU was later changed to Sofia
• after rejection, the task stayed in Diksha's Collect Approvals bin instead of moving to the current BU