monthly access review stuck after manager change: approver lookup failed error

TL;DR

Reroute the in-flight items, do not wait for the directory to heal on its own, because reviews have deadlines and the old manager will never act. List items assigned to the departed or changed managers, confirm each user new manager from the HR record, and reassign the items in the review platform to the new manager or to a named fallback approver where the new manager is not yet in role. Then fix the routing source so the next monthly cycle reads the updated hierarchy the first time.

monthly access review stuck after manager change: approver lookup failed error

Use this when

• Review items sit with a manager who left, moved teams or no longer manages those users.
• A reorganization happened between review launch and completion.
• Reminders go to the wrong person and progress stalls for whole teams.

Not for this skill when

• The manager is unchanged and active but not acting. Use escalation and reminder handling instead.
• The campaign has not launched yet. Correct the hierarchy data before launch and no rerouting is needed.

Steps

1. Export the stuck items grouped by current approver and filter to approvers who have left or whose reports changed in the reorganization window. Verify: stuck items are grouped under the affected approvers only.
2. For a sample of affected users, confirm the current manager from the HR system of record and compare it with the manager value in the identity platform the review reads. Verify: any hierarchy lag between HR and the identity platform is proven.
3. Correct the manager values in the identity platform through its normal HR sync or a governed bulk update for the affected population, avoiding one off edits that the next sync will overwrite. Verify: sampled users now show the new manager in the identity platform.
4. Reassign the in-flight review items to the new managers inside the campaign, using the platform reassign function so the audit trail shows the change and its reason. Verify: items show the new approver with a recorded reassignment reason.
5. Where a new manager is not yet appointed, assign items to the named interim approver or the manager own manager as policy allows, and note the interim basis on those items. Verify: no item remains with a departed or vacant approver.
6. Notify the new approvers of their inherited items and the real deadline, and confirm at least one from each affected team opens and decides an item. Verify: new approvers are actively deciding items.
7. Run a hierarchy freshness check before the next monthly launch comparing HR and platform manager data for the whole population, and file the check with this cycle evidence. Verify: the pre-launch check exists and its mismatch rate is recorded.

Why it happens

Manager changes are normal; the failure is that review platforms snapshot approvers at launch and directories update on their own schedule, so a mid-cycle reorganization strands items with people who no longer own the decision. The fix has two halves that are often confused: rerouting the live items so this cycle finishes, and repairing the hierarchy feed so next cycle starts right. Skipping the second half guarantees a repeat performance at the next reorganization, which in most companies is never far away.

Variants and edge cases

access review approver left company mid campaign

The departure phrasing. Reassign with the platform function, not by asking the new manager to use the old account or link.

review items assigned to old manager after reorg

The reorg phrasing. Sample HR against the platform first; sometimes only the campaign snapshot is stale, not the directory.

manager hierarchy out of date in Okta or SailPoint review

The data phrasing. Fix through the sync or a governed update that survives the next sync.

Edge cases to check before closing the review cycle:

• Acting managers may lack the context for their inherited teams access. Pair reassignment with a short briefing note per team.
• A user whose manager field is blank needs a policy answer, often the department head, decided before launch, not during the stall.
• Reassignment changes who is accountable for the decision. The audit trail must show the reason as reorganization, not leave it blank.

Compatibility: Access review campaigns in Okta, SailPoint and Entra, HR manager hierarchy feeds, campaign reassignment functions.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_TQsIGcnAwhBUKPEeluqFJA

Resolved from the public thread: https://vectle.com/posts/pst_TQsIGcnAwhBUKPEeluqFJA

Thread query: monthly access review stuck after manager change: approver lookup failed error

TL;DR: Reroute the in-flight items, do not wait for the directory to heal on its own, because reviews have deadlines and the old manager will never act. List items assigned to the departed or changed managers, confirm each user new manager from the HR record, and reassign the items in the review platform to the new manager or to a named fallback approver where the new manager is not yet in role. Then fix the routing source so the next monthly cycle reads the updated hierarchy the first time.