Handover job failed
You see a “Handover job failed” banner on a handover in the Handovers list (/admin/admin-security/handovers).
What’s happening
Section titled “What’s happening”The handover job checks a few things before it moves anything. If a check fails, the job stops and records the exact reason, and the banner shows that reason. The whole handover runs as one step, so nothing is ever half-transferred. When it fails, no roles moved and the outgoing admin’s account is unchanged.
The reasons you can see, and what to do:
| Banner says | What to do |
|---|---|
| The successor’s admin account is suspended / has been revoked / is still an invitation that hasn’t been accepted / was archived by an earlier handover … | Start a new handover and choose a successor who is an active admin. |
| The successor’s admin account no longer exists in this organization … | Start a new handover and choose an active successor. |
| The successor is the same admin as the outgoing admin … | Start a new handover and choose a different successor. |
| The outgoing admin’s account has been revoked / is still an invitation that hasn’t been accepted / was already archived by an earlier handover … | There is nothing to hand over: that account can’t act as an admin. |
| The outgoing admin’s account no longer exists in this organization … | There is nothing to hand over. |
| The outgoing admin’s account is suspended, so the handover did not run … | A suspension stops that admin’s pending handover. Nothing moved, and the account is unchanged. To give the successor the roles anyway, another admin can assign them directly — see Assign a role to an admin. |
| The outgoing admin is this organization’s only Org Owner, and holds that role through a group binding … | Give the successor the Org Owner role directly — see Assign a role to an admin — then start a new handover. |
| No successor admin is recorded on this handover … | Start a new handover and choose an existing active admin. |
| The handover stopped on an internal error after N attempts … | The job was retried automatically before it gave up, or it stopped and couldn’t be run again. Click Retry. |
An old failed handover may say “The handover failed before a cause was recorded. Nothing was transferred.” Start a new handover.
How to fix it
Section titled “How to fix it”- Fix the cause the banner names, if there is one to fix (for example, pick a different successor).
- Click Retry on the banner. It starts a new handover with the same outgoing admin, successor and transfer choices. The failed one stays in the list as history.
- If you need a different successor, start a new handover with New handover instead.
Retry shows only on your own failed handover (a handover always hands over the signed-in admin’s own account, so another admin’s failed handover can only be retried by them), and only if you have permission to run handovers. It also needs the failed handover to name a successor, and no newer handover for the same admin. If Retry says “A handover is already active for this admin, so a retry can’t start until it finishes.”, wait for that handover to finish.
Retry needs a recent sign-in. If a Confirm it’s you box opens, confirm your identity: you sign in again and come back to the list, then click Retry again. If you close the box instead, the card says “Retrying this handover needs a more recent sign-in.” and nothing was started.
If that didn’t work
Section titled “If that didn’t work”If the new handover fails too, its banner names the new reason. The outgoing admin keeps their access until a handover completes. Your organization doesn’t lose access while you sort it out.
- You can give the successor the roles they need yourself — see Assign a role to an admin.