HRIS S3 connector sync error: Worker doesn't exist

This page helps you resolve a synchronization error where a position references a worker that can't be found in your data.

Symptom

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

Position with external ID {externalId} is filled by a worker that doesn't exist

Cause

This error has two possible causes:

• CSV misconfiguration: The worker assigned to the position is missing from your workers report CSV, or the workerExternalId in the positions report CSV doesn't match any entry in the workers report CSV.

• Sync flow issue: The worker exists in your CSV but was lost somewhere in the connector → Teamwork Graph → Talent sync flow.

Resolution

Step 1: Verify the worker exists in your CSV files

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

2. In the positions report CSV, search for the positionId that matches the {externalId} from the error message.

3. Copy the workerExternalId value for that position.

4. In the workers report CSV, search for a worker with a workerId that matches the value you copied.

Step 2: Fix the issue based on what you found

If no matching worker is found, take one of the following actions:

• Update your workers report CSV to include the missing worker with the correct workerId.

• Update the affected position in your positions report CSV to reference a workerExternalId that already exists in your workers report CSV.

Once updated, upload the CSV files to your S3 bucket.

If a matching worker is found, this may indicate an issue in the sync flow rather than a CSV misconfiguration. Contact Atlassian Support for further investigation.

Step 3: 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.