Core HR requires a hire date before it will accept an employee record, and it requires that termination reason names be unique before it will save them. Both checks run while data is being written into Core HR, not while Core HR is being read from. When either check fails, Core HR rejects only the one record that failed the check. Everything else in that sync step continues. The two messages below show up under different entity rows in the sync log, so check the right row before you start troubleshooting.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| HireDate is required by Core HR. The employee will not be written to Core HR. | Write, into Core HR | The employee's hire date and rehire date are both blank. Only a blank value trips this check; a placeholder or default date is treated as a real date and will not raise this message. | The whole employee record is skipped. Nothing for that employee is written to Core HR in this run. | Enter a hire date for the employee in the source system, then re-run the sync. |
| A Termination Reason with Name of '[termination reason name]' has been sent to Core HR multiple times. Only the first Termination Reason with this Name will be saved. Employee's associated with any of the duplicate Name will not have their Termination Reason set correctly. Correct the source data and run the sync again. | Write, into Core HR | Two or more termination reason entries sent to Core HR in the same sync run have the same Name, compared without regard to upper or lower case. The check only looks at entries sent earlier in this same run, not at reasons already saved in Core HR. | The duplicate termination reason entry is skipped. Only the first entry with that Name is saved. Other, non-duplicate termination reason entries in the same run are not affected. | Give each termination reason a unique Name in the source system, then re-run the sync. |
Confirming the Error
- Open the Sync History screen and find the sync execution in question.
- Open the step for the Core HR connector inside that execution.
- Find the right entity row. The hire date message appears under the Employees entity row. The termination reason message appears under the Termination Reasons entity row. These are two separate rows.
- Look at the Errors column for that entity row. A nonzero count means at least one error was logged for that entity.
- Open the errors list for that entity row and read the messages. The Warnings, Information, Failures, Added, Updated, and Unchanged columns are not where these two messages appear.
- Match each message against the fixed wording in this article, not against the value inside the single quotes. The employee name or termination reason name will differ per record; the sentence around it will not.
Resolving the Error
Hire Date Is Required by Core HR
- In the Sync History step, confirm which connector is configured as the source for this Core HR step.
- In that source system, open the affected employee's record and check the Hire Date field. If the employee was rehired, also check the Rehire Date field.
- Enter a hire date (or rehire date) for the employee. Either field is enough to satisfy this check.
- Save the change in the source system.
- Re-run the sync and open the Employees entity row in the new execution. Confirm the Errors count for that employee is gone and the employee shows under Added or Updated instead.
Termination Reason With Name Sent Multiple Times
- In the Sync History step, confirm which connector is configured as the source for this Core HR step.
- In that source system, open the list of termination reasons that feeds this sync.
- Find every entry that shares the Name called out in the message. Name matching ignores upper and lower case, so "Voluntary" and "voluntary" count as the same Name.
- Rename the duplicate entries so each termination reason has a unique Name.
- Save the change in the source system.
- Re-run the sync and open the Termination Reasons entity row in the new execution. Confirm the Errors count is gone and each reason shows under Added or Updated instead.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- You confirm the employee's hire date and rehire date are both already populated in the source system, and the error still appears after a re-run.
- You confirm all termination reason Names are already unique in the source system, and the duplicate error still appears after a re-run.
- The source system will not let you edit the Hire Date field or the termination reason Name field, so there is no self-service fix available.
- The Termination Reasons entity row does not appear at all in the sync step and you expect it to. Confirm with engineering whether that entity is enabled for this connector before troubleshooting further.