Core HR needs to assign a brand new internal record number to a person the first time that person is added, and Arcoro asks Core HR's own database for that number right before saving the new record. If Core HR's database does not hand back a number at that moment, Arcoro cannot create the record and skips that one employee for this run. This only happens on new hires being added for the first time. An employee who already exists in Core HR and is only being updated never goes through this step, so this message cannot apply to updates.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| The Sync could not generate a new Person_ID and will not be able to add this Employee. Try the Sync again and if the error continues to occur, contact Arcoro support. | Write (Arcoro to Core HR). Employees entity, during the save step for a new hire. | The employee being processed is a new Add, not an update, and the request Arcoro sends to Core HR's database for a new record number comes back with no number assigned. | That one employee is not created. Other employees in the run continue to be processed normally. | Retry the sync once, then escalate if the same employee fails again. |
Confirming the Error
- Open the sync execution in question in Sync History.
- Open the step for the Core HR connector in that execution.
- Find the row for the Employees entity.
- Check the Errors count on that row. This message adds to Errors, not to Failures. A non-zero Failures count on this row means something more severe happened, such as the step or the whole sync stopping, and that is a different problem, not this one. Do not treat a Failures count as confirmation of this message.
- Open the errors list for the Employees entity. Several unrelated write problems can share the same generic wording in that list, so the list alone may not point straight at this issue. If a detail view for the entry is available, check it against the exact sentence shown in the table above.
- Check whether the affected employee is a new hire being added for the first time, rather than an existing employee being updated. If the employee already exists in Core HR and was only being updated, this message does not apply and the real cause is something else.
Resolving the Error
- Confirm the affected employee is a new hire on this run, not an update.
- There is little you can change directly. The message is triggered by Core HR's own database not returning a new record number at the moment Arcoro asks for one; nothing in the connector's configuration controls this.
- Re-run the sync.
- If the same employee fails again on the retry, stop retrying and escalate instead.
- Confirm the fix by re-running the sync and checking that the employee now appears under Added for the Employees entity instead of in the Errors list.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- Escalate if a re-run of the sync produces the same error for the same employee.
- Escalate right away if more than one new hire in the same run hits this error. That points to a problem on the Core HR database side, not a one-off.
- Before escalating, capture: the sync execution identifier, the connector, the affected employee, the timestamp of the run, and whether a re-run reproduced the error.