Core HR organizes people under Facilities, Locations, Job Codes, and Business Units (employers), and each of these needs a unique Name or Code to be saved correctly. When a Facility, Location, or Job Code arrives without its required Name or Code, or when the same Name or Code arrives twice in the same sync, Core HR only keeps the first one and skips the rest. Separately, an employee's record can be skipped if Core HR cannot work out which facility or employer the employee belongs to, for example, when the employee already exists under a different facility than the connector is configured for, or when the employee is tied to more than one employer.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Facility Name is required. Item will not be synced to Core HR. | Arcoro to Core HR (write) | The Facility being written has no value in the Name field. Checked before the duplicate check, so this occurs instead of the duplicate message when Name is blank. | Whole record skipped. This Facility is not created or updated in Core HR. | Add a Name to the Facility in the source system and run the sync again. |
| Facility Code 1 is required. Item will not be synced to Core HR. | Arcoro to Core HR (write) | The Facility being written has no value in the Facility Code 1 field. Checked in the same pass as the Name check, so a Facility missing both fields logs both messages. | Whole record skipped. This Facility is not created or updated in Core HR. | Add a Facility Code 1 to the Facility in the source system and run the sync again. |
| A Facility with a value of '[Facility Name]' has been sent to Core HR multiple times. Only the first Facility with this value will be saved. Employee's associated with duplicate values will not have their Facility set correctly. Correct the source data and run the sync again. | Arcoro to Core HR (write) | A Facility Name (matched case-insensitively) has already been sent to Core HR earlier in this same sync run. Only checked after the Name and Facility Code 1 required-field checks pass. | Whole record skipped. Only the first Facility with that Name is saved; later ones with the same Name are dropped for this run. | In the source system, give each Facility a unique Name and run the sync again. |
| Location Name is required. Item will not be synced to Core HR. | Arcoro to Core HR (write) | The Location being written has no value in the Name field. | Whole record skipped. This Location is not created or updated in Core HR. | Add a Name to the Location in the source system and run the sync again. |
| A Location with a value of '[Location Name]' has been sent to Core HR multiple times. Only the first Location with this value will be saved. Employee's associated with duplicate values will not have their Facility set correctly. Correct the source data and run the sync again. | Arcoro to Core HR (write) | A Location Name (matched case-insensitively) has already been sent to Core HR earlier in this same sync run. | Whole record skipped. Only the first Location with that Name is saved; later ones with the same Name are dropped for this run. | In the source system, give each Location a unique Name and run the sync again. |
| A Job Code with a Display Value of '[Job Code Description]' has been sent to Core HR multiple times. Only the first Job Code with this Display Value will be saved. Employee's associated with any of the duplicate Display Values will not have their Job Code Local set correctly. Correct the source data and run the sync again. | Arcoro to Core HR (write) | A Job Code's Code value (matched case-insensitively) has already been sent to Core HR earlier in this same sync run. The Code is the actual match key; the value quoted in the message is the Job Code's Description (its Display Value), not the Code. | Whole record skipped. Only the first Job Code with that Code is saved; later ones with the same Code are dropped for this run. | In the source system, give each Job Code a unique Code and run the sync again. |
| An existing Employee was found in Core HR matching on [SSN or Employee Identifier] assigned to another facility. The record will be skipped during this Sync. If the employee should be assigned to facility [connector's configured Facility Code], please update their Facility Code information and run the Sync again. | Arcoro to Core HR (write) | Only possible when the connector has a single Facility Code configured in its connector settings. An existing Core HR employee is matched by SSN, or by Employee Identifier when no SSN match is found, but none of the matches belong to the connector's configured facility, while at least one match belongs to a different facility. | Whole record skipped. This employee is not created or updated in Core HR this run. | If the employee belongs to the connector's facility, update the employee's Facility Code assignment in Core HR to that facility and run the sync again. If the employee should stay on their current facility, this connector is not expected to process them. |
| The employee is assigned to more than one Business Unit (employer) in Core HR. Only a single Business Unit is supported. Assign a single Business Unit to this employee in Core HR and run the sync again. | Core HR to Arcoro (read) | Business Unit reading is active for this connector, meaning either the Business Unit employee scope is enabled, or the connector is the Core HR For Viewpoint Spectrum configuration with the Map Facility 1 Code as Company Code setting turned off. In addition, the employee has more than one payroll account (employer) assignment in Core HR. | Whole record skipped. This employee is not read into Arcoro this run. | In Core HR, remove the extra employer (payroll account) assignment so the employee has only one, then run the sync again. |
| The Business Unit (employer) assigned to this employee does not have a Name in Core HR. A Business Unit Name is required to sync this employee. Add a Name to the employer in Core HR and run the sync again. | Core HR to Arcoro (read) | The Business Unit employee scope is enabled, the employee has exactly one assigned employer (employees with more than one are caught by the message above first), a matching employer setup record exists for that employer, and that record's Employer Name field is blank. | Whole record skipped. This employee is not read into Arcoro this run. | In Core HR, add a Name to the employer record and run the sync again. |
| Reading Core HR's [Core HR source property] property to populate the Arcoro Employee Model's [Facility] property does not appear to have worked as expected. The property is required and the employee will not be synced. Correct the data and run the sync again. | Core HR to Arcoro (read) | Only occurs on the Core HR For Viewpoint Spectrum connector configuration, while mapping the employee's Facility. If the Map Facility 1 Code as Company Code connector setting is off, this occurs when the employee's assigned employer has no value in its External Employer Code field, or the employee has no assigned employer at all, and is reported as the Employer (External Employer Code) property. If that setting is on, this occurs when the employee's Facility 1 does not resolve to a value through the Facility Code 1 lookup, and is reported as the Facility Code1 property. Either way the resulting Facility value is empty. | Whole record skipped. This employee is not read into Arcoro this run. | In Core HR, either give the employee's employer an External Employer Code, or correct the employee's Facility 1 assignment so it resolves to a Facility Code 1, depending on which connector setting is in use, then run the sync again. |
Confirming the Error
- Open the sync execution for the affected run in Sync History.
- Find the step for the Core HR connector in that execution.
- Find the entity row for Facility, Location, Job Code, or Employees, depending on which record was reported.
- Check the Errors column for that entity row. A non-zero count means at least one item logged an error.
- Open the errors list for that entity and match the fixed part of the sentence against the Message text column in the table above. Ignore the quoted value in single quotes or brackets, since that is the specific Facility, Location, Job Code, or match type for you.
- Confirm the Added, Updated, and Unchanged counts for that entity to see that other records in the same run were not affected.
Resolving the Error
Facility Name, Facility Code 1, or Location Name is Missing
- Identify the Facility or Location named in the sync log, or if the Name itself is blank, identify the record by its other details.
- In the source system Arcoro reads this data from, add the missing Name or Facility Code 1 value to that Facility or Location.
- Run the sync again and confirm the record no longer appears in the entity's errors list.
The Same Facility, Location, or Job Code Was Sent to Core HR More Than Once in One Sync
- In the source system, search for other Facility, Location, or Job Code records that share the same Name (Facility or Location) or Code (Job Code), ignoring case.
- Correct or deactivate the duplicate so each Name or Code is unique.
- Run the sync again and confirm only one record with that value appears, and that it is no longer in the errors list.
An Employee Already Exists in Core HR Under a Different Facility Than the Connector
- In the connector's configuration, check the Facility Code setting to see which facility this connector is restricted to.
- Decide whether the employee should move to that facility. If so, in Core HR update the employee's Facility Code assignment to the connector's configured facility.
- If the employee should stay on their current facility, no change is needed in Core HR; this connector is not expected to sync that employee.
- Run the sync again and confirm the employee no longer appears in the Employees errors list, if the facility assignment was changed.
The Employee Has More Than One Employer (Business Unit) Assigned in Core HR
- In Core HR, open the employee's payroll account assignments.
- Remove or correct the extra assignment so the employee has exactly one employer.
- Run the sync again and confirm the employee no longer appears in the Employees errors list.
The Employer (Business Unit) Is Missing a Name in Core HR
- In Core HR, open the employer record assigned to the affected employee.
- Add a Name to that employer record.
- Run the sync again and confirm the employee no longer appears in the Employees errors list.
The Employee’s Facility Could Not Be Determined (Core HR for Viewpoint Spectrum Connectors Only)
- Confirm the connector uses the Core HR For Viewpoint Spectrum configuration and check whether its Map Facility 1 Code as Company Code setting is on or off.
- If that setting is off, in Core HR add an External Employer Code to the employee's assigned employer, or assign the employee to an employer that has one.
- If that setting is on, in Core HR correct the employee's Facility 1 assignment so it resolves to a Facility Code 1 value.
- Run the sync again and confirm the employee no longer appears in the Employees errors list.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The same message still appears after the source data has been corrected and the sync has been run again.
- The log text does not match any message text in the table above; it may belong to a different article or be a message passed through from Core HR itself.
- You are unsure whether the connector's Facility Code setting, Business Unit scope, or Core HR for Viewpoint Spectrum configuration is set correctly, since changing connector configuration is not a tier 1 change.
- The employee facility mismatch message appears and it is unclear whether the employee should be reassigned to the connector's facility or excluded from this connector.