ServiceNow access certification task assignment failed: user lookup error fix

TL;DR

Find the exact user reference the task tried to resolve before you reassign anything, because a lookup failure means the reference itself is broken. Open a failed task, read the assignment rule inputs, and check the target user record for an inactive state, a duplicate, or a key that the import changed. Fix the user record or the transform that produces the reference, regenerate one task to prove assignment works, and only then regenerate the batch.

ServiceNow access certification task assignment failed: user lookup error fix

Use this when

• Certification tasks are created unassigned with a lookup error in the task log.
• Tasks for one department or location fail while others assign normally.
• A recent user import or HR sync preceded the failures.

Not for this skill when

• Tasks assign but approvers are on leave. Use delegation settings instead.
• The campaign will not launch at all. Resolve the campaign definition first.

Steps

1. Open a failed certification task and copy the lookup error, the assignment rule name and the user reference value the rule tried to resolve. Verify: the failing reference value is recorded exactly.
2. Search the user table for that reference and check whether it returns no record, a duplicate pair or an inactive record, noting which case applies. Verify: the record state is classified as missing, duplicate or inactive.
3. If an import ran recently, open its transform history and look for skipped or errored rows carrying the same reference, especially changed employee numbers or email based keys. Verify: any import error for the reference is found and noted.
4. Repair the root record, merging duplicates, reactivating a wrongly inactivated user or correcting the key field, following the instance user administration process. Verify: a single active user record now matches the reference.
5. Check the manager or approver field on that record as well, since assignment chains often fail on the second lookup even when the first succeeds. Verify: the approver field resolves to an active user too.
6. Regenerate or reassign one test task using the same rule and confirm it lands in the right inbox with the right due date. Verify: the test task is assigned correctly end to end.
7. Regenerate the failed batch, confirm the unassigned count drops to zero, and record the import or record fix in the campaign evidence. Verify: the batch shows no remaining lookup failures.

Why it happens

ServiceNow assignment depends on references staying stable across imports. When an HR feed changes the key it sends, or a cleanup inactivates a record that tasks still point at, the rule has a reference that resolves to nothing and the task is born unassigned. The instance rarely loses the user entirely; more often the record is duplicated, inactive or keyed differently than the task expects. Repairing the record layer fixes the whole batch at once, whereas manual reassignment leaves the next campaign to fail the same way.

Variants and edge cases

certification tasks unassigned in ServiceNow

The queue phrasing. Start from one task and one reference rather than bulk reassigning the queue.

sys_user lookup failed during task generation

The platform phrasing using the user table name. Check duplicates first; imports frequently create a second record instead of updating.

access certification approver not found after HR sync

The sync phrasing. Compare the keys the sync sends now with the keys tasks were built with last cycle.

Edge cases to check before closing the review cycle:

• Inactive does not always mean wrong; a termed user tasks should close as not applicable, not be reassigned to a stranger.
• Lookup errors on the manager field often trace to a manager who is a group, not a person. Route those to a fallback approver group.
• Test regeneration in a sub-production instance when the batch is large and the import fix is unproven.

Compatibility: ServiceNow certification and access review tasks, user administration and import set transforms, current supported ServiceNow releases.

Provenance

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