These messages fire when Arcoro cannot uniquely identify an employee, or when a required identity field is missing or invalid. Two of them happen while reading employee data out of Core HR, because Core HR itself has a blank or a duplicate Employee ID. The rest happen while writing an employee, an Ethnicity code, or an I9 Status code into Core HR, because the incoming record is missing a required value, has an invalid Employee Identifier, or matches more than one existing employee in Core HR. In every case, only the one record involved is skipped for that sync run.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Source record does not have a social security number or Employee Identifier. Employee will not be written to Core HR. | Write (source into Core HR) | The incoming employee record has no value in both the Social Security Number field and the Employee Identifier field. | Whole record skipped. This employee is not written to Core HR. | Add a Social Security Number or an Employee Identifier to the employee in the source system. |
| Employee Identifier is required and must contain only alphanumeric characters. The employee will not be written to Core HR. | Write (source into Core HR) | The incoming Employee Identifier has a value, but that value contains at least one character that is not a letter or a number, including spaces, hyphens, and punctuation. | Whole record skipped. | Remove any spaces, hyphens, or other symbols from the Employee Identifier in the source system. |
| Employee does not have a valid ID value and will not be read. Correct the data in Core HR and execute the Sync again. | Read (Core HR into Arcoro) | The employee record in Core HR has a blank Employee ID. | Whole record skipped. This employee is not read from Core HR. | Enter an Employee ID on the employee record in Core HR. |
| Employee ID is not unique. Employee records with Employee ID: '[Employee ID]' will not be Synced. Correct the data in Core HR and execute the Sync again. | Read (Core HR into Arcoro) | More than one Core HR employee record shares the same Employee ID. Records terminated before December 1 of the prior year are excluded from this check unless the termination date is before the hire date, and if the connector is filtered to a facility or a specific list of Employee IDs, only records inside that filter count. | Whole record skipped. None of the employees sharing that Employee ID are read. | Change the Employee ID on one of the duplicate employee records in Core HR so it is unique. |
| Duplicate employees found in Core HR matching on [SSN or Employee Identifier]. The Sync requires that Core HR contain a single employee matching on SSN or Employee ID. The employee will not be synced. | Write (source into Core HR) | While writing, Arcoro looks in Core HR for the one existing employee matching the incoming record by Social Security Number, or by Employee Identifier if there is no Social Security Number or no match by number, and finds two or more existing Core HR employees that match. If the connector is restricted to a facility, only Core HR employees in that facility, or with no facility set, are counted. | Whole record skipped. This employee is not written to Core HR. | Correct the duplicate employee records in Core HR so only one employee has that Social Security Number or Employee Identifier. |
| Duplicate Employee updates sent from source system matched by [SSN or Employee Identifier] in Core HR. Only the first source record will be Synced. Source Employee: [Employee Identifier] will not be used. | Write (source into Core HR) | Two different employee records from the source data match to the same existing Core HR employee by Social Security Number or Employee Identifier. The first source record processed is written; each later source record that matches the same Core HR employee triggers this message. | Whole record skipped, for the later source record only. The first source record for that Core HR employee still writes normally. | Correct the Social Security Number or Employee Identifier in the source system so no two source employees point to the same Core HR employee. |
| Missing Ethnicity. Item will not be synced to Core HR. | Write (source into Core HR) | An entry in the Ethnicities list has no Ethnicity value at all. | Collection item skipped. This one Ethnicity entry is not written; it is not tied to a single employee record. | Provide an Ethnicity value for the entry in the source system, or remove the blank entry. |
| Null value sent for Ethnicity. Item will not be synced to Core HR. | Write (source into Core HR) | An entry in the Ethnicities list is sent with the specific "Null" Ethnicity value rather than a blank field or a real value. | Collection item skipped. | Set a real Ethnicity value in the source system, or remove the entry if it should not be tracked. |
| A Ethnicity with a Display Value of '[Ethnicity value]' has been sent to Core HR multiple times. Only the first Ethnicity with this Display Value will be saved. Employees associated with any of the duplicate Display Values will not have their Ethnicity set correctly. Correct the source data and run the sync again. | Write (source into Core HR) | The same Ethnicity Display Value is sent more than once in the same sync run. Only the first occurrence is kept. | Collection item skipped for every occurrence after the first. Any employee whose Ethnicity depends on the skipped entry still syncs, but that employee's Ethnicity field is not set correctly. | Remove or correct the duplicate Ethnicity entries in the source system so each Display Value appears only once. |
| An I9 Status with Name of '[I9 Status name]' has been sent to Core HR multiple times. Only the first I9 Status with this Name will be saved. Employee's associated with any of the duplicate Name will not have their I9 Status set correctly. Correct the source data and run the sync again. | Write (source into Core HR) | The same I9 Status Name is sent more than once in the same sync run. Only the first occurrence is kept. | Collection item skipped for every occurrence after the first. Any employee whose I9 Status depends on the skipped entry still syncs, but that employee's I9 Status field is not set correctly. | Remove or correct the duplicate I9 Status entries in the source system so each Name appears only once. |
Confirming the Error
- Open the sync execution in Sync History for the run in question.
- Find the step for the Core HR connector. For the two Employee ID messages, use the step where Core HR is the source. For every other message in this article, use the step where Core HR is the destination.
- Locate the entity row. Employee identity messages appear under the Employees entity row. Ethnicity messages appear under the Ethnicities entity row. I9 Status messages appear under the I9 Statuses entity row.
- Check the Errors column for that entity row. If it is greater than zero, open the errors list for that row.
- Match the reported problem against the fixed part of each message in the table above, ignoring the quoted employee ID, name, or Display Value. The wording around the quoted value is what identifies the message, not the value itself.
- Note the Added, Updated, and Unchanged counts on the same row to confirm every other record in that step still processed.
Resolving the Error
Social Security Number or Employee Identifier Missing
- In the source system for this sync step, open the employee's record.
- Enter a value in either the Social Security Number field or the Employee Identifier field. Only one of the two is required.
- Re-run the sync and confirm the employee no longer appears in the Employees errors list.
Employee Identifier Contains Invalid Characters
- In the source system for this sync step, open the employee's record.
- Edit the Employee Identifier field so it contains only letters and numbers. Remove any spaces, hyphens, or punctuation.
- Re-run the sync and confirm the employee no longer appears in the Employees errors list.
Employee ID Missing in Core HR
- In Core HR, open the employee's record.
- Enter a value in the Employee ID field.
- Re-run the sync and confirm the employee is now read.
Duplicate Employee ID in Core HR
- In Core HR, find the employee records that share the reported Employee ID.
- Change the Employee ID on one of the records so each active employee has a unique value.
- Re-run the sync and confirm both employees are now read without this message.
Duplicate Employee Match in Core HR
- In Core HR, search for existing employees with the same Social Security Number or Employee Identifier reported in the message.
- Correct or merge the duplicate employee records in Core HR so only one employee remains with that value.
- Re-run the sync and confirm the employee now writes successfully.
Duplicate Source Employee Records
- In the source system for this sync step, find the employee records reported as duplicates. The message names the source Employee Identifier that was skipped.
- Correct the Social Security Number or Employee Identifier on the source records so no two employees point to the same Core HR employee.
- Re-run the sync and confirm both source employees now write to separate Core HR employees, or that the record that should not sync has been removed from the source.
Missing or Null Ethnicity Value
- In the source system for this sync step, find the Ethnicity entry named in the sync log.
- Enter a real Ethnicity value, or remove the entry if it is not needed.
- Re-run the sync and confirm the entry no longer appears in the Ethnicities errors list.
Duplicate Ethnicity Value
- In the source system for this sync step, find every Ethnicity entry with the Display Value named in the message.
- Remove or correct the duplicate entries so the Display Value appears only once.
- Re-run the sync and confirm the Ethnicities row no longer shows this message, then confirm any affected employee's Ethnicity field is now set.
Duplicate I9 Status Value
- In the source system for this sync step, find every I9 Status entry with the Name named in the message.
- Remove or correct the duplicate entries so the Name appears only once.
- Re-run the sync and confirm the I9 Statuses row no longer shows this message, then confirm any affected employee's I9 Status field is now set.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The message persists after the named field has been corrected and the sync has been re-run.
- The Errors column shows a count for the Employees, Ethnicities, or I9 Statuses row, but the message text in the log does not match any row in the table above.
- The employee, Ethnicity, or I9 Status still will not sync after multiple attempts to correct the source or Core HR data.
- A duplicate employee match message keeps appearing for a Social Security Number or Employee Identifier, but there is not a duplicate. That points to data the agent cannot see or resolve without a developer reviewing the match.