HRIS S3 connector sync error: Organization doesn't exist

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

Symptom

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

Position with external ID {externalId} is associated with an organization that doesn't exist

Cause

This error has two possible causes:

• CSV misconfiguration: The supervisory organization assigned to the position is missing from your organizations report CSV, or the supervisoryOrganizationId in the positions report CSV doesn't match any entry in the organizations report CSV.

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

Resolution

Step 1: Verify the organization exists in your CSV files

1. Download your positions report CSV and organizations 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 supervisoryOrganizationId value for that position.

4. In the organizations report CSV, search for an organization with an organizationId that matches the value you copied.

Step 2: Fix the issue based on what you found

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

• Update your organizations report CSV to include the missing organization with the correct organizationId.

• Update the affected position in your positions report CSV to reference an organizationId that already exists in your organizations report CSV.

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

If a matching organization is found, this may indicate an issue in the connector 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.