Skip to content
English
Create Ticket
  • There are no suggestions because the search field is empty.

Resolve Google Admin Console restore error: Group Member Already Exists

The membership was reported as failed because the person is already a member of the group. No data was lost.

Applies to: Group members

 What this error means

SysCloud tried to add someone whose requested membership is already present.

 Why this error occurs

Google refuses to add a membership that already exists, so the row is reported as failed even though the group is already in exactly the state you asked for. Three situations produce this with a perfectly valid request:

  • An in-place or compare-with-cloud restore where the membership was never actually lost.
  • The same restore run twice.
  • The case most often missed: the member is added by an alias address while their primary address is already in the group. Google resolves the alias to the same person.

 Resolution

  1. In the Google Admin console, go to Menu > Directory > Groups.
  2. Open the affected group and click Members.
  3. Confirm the person appears in the list. If they are not listed, click Direct and indirect members, which also shows people who are members through a nested group.
  4. If the membership is present, whether direct or indirect, no action is required.
  5. If you still cannot find them, check whether the address in the error is an alias. Open the user in Directory > Users and compare their primary address with the addresses already in the group.

 Verify the resolution

Confirm in the Google Admin console that the affected group already contains the expected members. The report may still show the original row as failed, but no data is missing. 

 If the error continues

Escalate only if the expected membership is genuinely absent from the group, including indirect memberships and aliases. In that case, contact SysCloud Support with the group address, member address, error code, job ID, and time of failure.