View and troubleshoot sync errors

Position with external ID <external ID> is managed by a position that doesn’t exist

A position in your data references a manager position that is missing or not set up correctly. The issue can be caused by a configuration problem or a sync issue between your HR system and Atlassian.

Follow these steps to fix the Positions and Supervisory Orgs reports.

The position/worker/organization file does not follow the required format for this connector.

The file at the specified S3 path is not in a supported format. The HRIS S3 connector only supports CSV files.

Check that the S3 file path for the position file is correct, and make sure the file is a CSV file.

The position/worker/organization CSV file is missing the required column(s):

The specified CSV file is missing one or more required columns.

Compare your CSV headers against the required headers for the HRIS S3 connector. Add any missing columns and upload the updated file.

The position/worker/organization file URL is invalid. Please check and try again.

The position, worker, or organization file S3 URI is empty or in an invalid format.

In your AWS account, copy the full S3 URI for the file and paste it into the corresponding file path field in the connector setup screen.

Row parsing error: position at row {rowNumber}

There is an unexpected formatting issue with the position CSV row at the given row number.

Open the position CSV file, go to the row number in the error message, and fix any formatting issues, such as missing delimiters or unmatched quotes.

position with ID {entityId} at row {rowNumber} is missing required field ‘{fieldName}’

The position row is missing a value in a required column.

Open the position CSV file, find the row and entity ID from the error message, and add the missing value.

worker with ID {entityId} at row {rowNumber} is missing required field ‘{fieldName}’

The worker row is missing a value in a required column.

Open the worker CSV file, find the row and entity ID, and add the missing value.

organization with ID {entityId} at row {rowNumber} is missing required field ‘{fieldName}’

The organization row is missing a value in a required column.

Open the organization CSV file, find the row and entity ID, and add the missing value.

position with ID {entityId} at row {rowNumber} has invalid format ‘{actualValue}’ for field ‘{fieldName}’

The position row has a value that does not match the expected format for that field.

Open the position CSV file, find the row and entity ID, and update the field value to the correct format.

worker with ID {entityId} at row {rowNumber} has invalid format ‘{actualValue}’ for field ‘{fieldName}’

The worker row has a value that does not match the expected format for that field.

Open the worker CSV file, find the row and entity ID, and update the field value to the correct format.

organization with ID {entityId} at row {rowNumber} has invalid format ‘{actualValue}’ for field ‘{fieldName}’

The organization row has a value that does not match the expected format for that field.

Open the organization CSV file, find the row and entity ID, and update the field value to the correct format.

Invalid email format in Worker CSV file at row {rowNumber}.

The worker CSV file contains an email address that is not in a valid format.

Open the worker CSV file, go to the row in the error message, and fix the email address format or remove the email address.

Duplicate position found with ID {entityId} at row {rowNumber}.

The position CSV file contains a duplicate position ID. Each ID must be unique.

Open the position CSV file, find the rows with the duplicate ID, and change one of the IDs to a unique value.

Duplicate worker found with ID {entityId} at row {rowNumber}.

The worker CSV file contains a duplicate worker ID. Each ID must be unique.

Open the worker CSV file, find the rows with the duplicate ID, and change one of the IDs to a unique value.

Duplicate organization found with ID {entityId} at row {rowNumber}.

The organization CSV file contains a duplicate organization ID. Each ID must be unique.

Open the organization CSV file, find the rows with the duplicate ID, and change one of the IDs to a unique value.

The specified S3 object was not found. Please verify the file path and try again.

The connector could access the S3 bucket, but did not find an object that matches the file path you provided.

Check that the S3 URI for each file is correct, and make sure an object exists in the bucket at that path. If needed, update the file path or upload the CSV file to the correct path.

Access denied to the S3 resource. Please check your permissions and try again.

The connector assumed the AWS role, but the role does not have permission to read the S3 file.

Check that the S3 file URIs are correct. In AWS, update the role policy so it can read the S3 objects used by the connector.

S3 bucket not found or not accessible. Please verify the bucket name and permissions.

The connector assumed the AWS role, but could not access the S3 bucket.

Check that the bucket name in each S3 URI is correct, that the bucket exists and is available, and that the role has permission to access the bucket.

Invalid S3 URL format. Please provide a valid S3 URL.

One or more S3 URIs are empty or in an invalid format.

In your AWS account, copy the full S3 URI for each file and paste it into the file path fields in the connector.

Failed to assume AWS role. Please check your role configuration and permissions.

The connector could not assume the AWS role you provided.

Check that the Role ARN is correct, review the role’s trust policy in AWS, and make sure the HRIS S3 connector is allowed to assume the role. Then try saving the configuration again.