HRIS S3 connector sync error: Cyclical reporting line

This page helps you resolve a synchronization error where a reporting cycle is detected in your position or organization data.

Symptom

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

Position - cyclical reporting line detected in positions: {external ID 1} -> {external ID 2} -> {external ID 3} -> {external ID 1}.

Cause

Talent requires a clear hierarchy and doesn't allow cyclical reporting lines (where a position or organization eventually reports back to itself). This error occurs when your CSV data in S3 contains a loop in the managerPositionId or supervisoryOrganizationId assignments.

Resolution

To resolve this issue, you must identify the positions or organizations in the cycle and update your CSV data to break the loop.

Step 1: Identify the affected data

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

2. Search for the IDs provided in the error message.

3. Trace the reporting line to confirm where the loop occurs.

Step 2: Break the cycle

You can resolve this in one of two ways:

Option 1: Update the positions report CSV

1. Open your positions report CSV.

2. Locate the positions identified in the error message.

3. Update at least one managerPositionId value so that the position no longer contributes to the loop.

Option 2: Update the organizations report CSV

1. Open your organizations report CSV.

2. Locate the organizations identified in the error message.

3. Update at least one supervisoryOrganizationId value to a different, valid organization that breaks the cycle.

Step 3: Upload and re-sync

1. Upload the updated CSV files to your S3 bucket.

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

3. Select the Settings tab.

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