This message is raised by Arcoro before the employee is ever sent to HCSS. It is not a rejection from HCSS, even though it lives in a family named for rejected writes. Arcoro checks the employee record for a set of required conditions, and if any of them fail, it stops and never issues a create or update request to HCSS at all.
This message never appears by itself, as there is a summary line that tells you the employee failed one or more checks, and it is always logged together with at least one other, more specific error that names the actual problem.
Messages in this article
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| The Employee has one or more validation errors. The employee will not be synced. Correct the data and run the Sync again. | Write (Arcoro to HCSS) | Fires once per employee, immediately after one or more of the eight specific validation checks in the routing table below have already logged their own error for that same employee in the same sync. | Whole employee record skipped. No create or update request is sent to HCSS for this employee on this run. | Do not act on this message alone. Read every other error logged for the same employee in the same sync step and fix those instead. |
Routing table: find the specific error logged alongside this one
More than one of the eight checks below can fail for the same employee in the same sync. Read the full list of errors for that employee before you start fixing anything, not just the first one you see.
| Message logged with it | What to fix | Related Article |
|---|---|---|
| Employee ID is required. | Populate the Employee ID on the employee record in Arcoro. | Employee identity and demographics |
| First Name is required. | Populate the employee's First Name on the employee record in Arcoro. | Employee identity and demographics |
| Last Name is required. | Populate the employee's Last Name on the employee record in Arcoro. | Employee identity and demographics |
| Employee is terminated, but the Termination Date is empty. Record will not be synced. | Add a Termination Date in Arcoro, or correct the Employment Status if the employee should not show as terminated. | Employment status, hire and termination dates |
| Employee is terminated, but Termination Date is in the future. Record will not be synced. | Correct the Termination Date in Arcoro so it is not a future date, or correct the Employment Status. | Employment status, hire and termination dates |
| Occupation '[occupation value]' exceeds max length of 100. Record will not be synced. | Shorten the value in the employee's Occupation field in Arcoro to 100 characters or fewer. This message is shipped with a misspelling of "Occupation" in the text; that is expected. | Union, classification, workers comp, occupation |
| Could not match Occupation '[occupation value]' with a Pay Class in HCSS. Record will not be synced. | Correct the Occupation value in Arcoro so it matches a Pay Class code that exists in HCSS, or have the Pay Class created in HCSS. If the employee has no Occupation set at all, this message shows the literal value 'Not Set'. | Union, classification, workers comp, occupation |
| No Business Unit was found on HCSS with a matching Code '[facility value]'. Correct the data and run the Sync again. | Correct the Facility value in Arcoro so it matches a Business Unit code that exists in HCSS, or have the Business Unit created in HCSS. | Missing Business Unit/Facility |
Confirming the Error
- Click "Sync History" and open the sync record with the sync error from the Arcoro sync history screen.
- Open the step for the HCSS connector.
- Find the employee entity row for that step.
- Check the Errors column for that row. A non-zero count is expected when this message appears; this message is logged as an error, not a failure, so the Failures column does not need to be non-zero for this message to be present.
- Open the errors list for that entity and locate the employee by name or identifier.
- Match on the fixed part of the sentence: "The Employee has one or more validation errors." Ignore any values in quotes when matching other messages, since those are specific to the employee.
- Read every error listed for that same employee, not just the first one. Expect at least two entries for that employee whenever this message is present: this message plus one or more of the eight specific messages in the routing table above.
Resolving the Error
- Open the full list of errors for the affected employee in the same sync step.
- Identify each specific message from the routing table above that appears alongside this one.
- Open the linked article for each specific message and follow its resolution steps.
- Identity, status, and occupation length corrections are made in Arcoro, on the employee record. Pay Class and Business Unit code corrections may require the code to be created in HCSS instead, if the code genuinely does not exist there.
- Once every specific error for that employee has been resolved, run the sync again.
- Confirm the fix worked by checking the same entity row: this rollup message clears only when every specific error for that employee has cleared, and the employee should now appear as Added or Updated 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.
- This message appears for an employee with no other error logged for that same employee in the same sync. The validation logic that raises this message only fires after one of the eight specific checks has already failed, so this should not be possible; treat it as a defect and escalate with the sync execution ID and the employee identifier.
- The message logged alongside this one does not match any of the eight messages in the routing table above and reads as text returned directly from HCSS rather than from Arcoro.
- The specific error has been corrected in the source data, the sync has been re-run, and this message still appears.