HRIS S3 connector sync error: Duplicate emails

This page helps you resolve a synchronization error where multiple active workers in your HRIS S3 data share the same email address.

Symptom

When syncing users with the HRIS S3 connector, the sync fails and you see the following error in your Talent logs:

Worker with external ID {externalId} - email: Duplicate email. Emails must be unique

Cause

Talent requires every active worker to have a unique email value. This error occurs when your workers report CSV contains multiple active rows with the same emailAddress.

Resolution

To resolve this issue, you must identify the duplicate email addresses in your CSV data and ensure each active worker has a unique entry.

Step 1: Identify the affected workers

1. Download your workers report CSV from your S3 bucket.

2. Search for the workerId that matches the {externalId} provided in the error message.

3. If you find only one worker (or none), the CSV data may have been updated since the last sync attempt. Try to re-sync the app to see if the issue is resolved.

4. If you find the worker, copy their emailAddress value and search the file for any other workers with a matching email.

Step 2: Check for active duplicates

1. Review the isActive column for all workers sharing the duplicate email address.

2. If only one worker has an isActive value of 1, the CSV data may have been updated since the last sync. Try to sync the connector again.

3. If multiple workers are marked as 1, continue to the next step.

Step 3: Fix the duplicate emails and upload

You can resolve this in one of two ways:

• Update your workers report CSV to give each active worker a unique emailAddress.

• Update the CSV so that only one worker with that email has an isActive value of 1. Set all other duplicates to 0.

Once you have updated the CSV file, upload the new copy to your S3 bucket.

Step 4: Re-sync

1. Go back to the HRIS S3 connector in Atlassian Administration (Connected apps > HRIS S3).

2. Select the Settings tab.

3. Select Sync now to sync the update that fixes the error.