HCSS is a write-only connector. Employee records flow from the source platform into HCSS, never the other way. Before Arcoro writes a terminated employee to HCSS, it checks that the employee has a termination date and that the date is not in the future. If either check fails, that employee's entire record is left out of the sync run and nothing is written to HCSS for them.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Employee is terminated but Termination Date is empty. Record will not be synced. | Write | The employee's status is Terminated and the Termination Date field is blank. | Whole record skipped for this sync run. | Enter a termination date on the employee record in the source system. |
| Employee is terminated but Termination Date is in the future. Record will not be synced. | Write | The employee's status is Terminated and the Termination Date is later than the current date and time. | Whole record skipped for this sync run. | Wait for the termination date to arrive, or correct the date if it was entered wrong. |
Both checks only run for an employee whose status is Terminated. An employee in any other status never triggers either message. The two checks are separate tests, not either/or: the empty-date check requires the date to be blank, and the future-date check requires a date to be present and later than the current moment, so in practice only one of the two can fire for the same employee in the same sync.
The future-date check compares the termination date against the current date and time, not against the current date alone. This is a full date-and-time comparison. See Open questions below for what this means for a termination date entered as "today."
Confirming the Error
- Click "Sync History" and open the sync record with the sync error from the Arcoro sync history screen.
- Select the step for the HCSS connector.
- Find the employee row for the affected employee in that step.
- Open the Errors list for that employee row and confirm the message text matches one of the two listed above.
The Sync History screen shows per-entity counts in columns labelled Errors, Warnings, Information, Failures, Added, Updated, and Unchanged. For this set, a non-zero Errors count on the employee row is what corresponds to these two messages. A non-zero Failures count reflects a different kind of problem (a rejected or interrupted write) and is not caused by either message in this article.
Resolving the Error
Employee is Terminated, but Termination Date is Empty
- Open the employee's record in the source system (the platform they sync from into HCSS) and confirm the employee's status is set to Terminated.
- Enter a termination date on that same employee record.
- Run the sync again.
- Confirm in the sync log that the employee row no longer shows this message and that the employee was added or updated in HCSS.
Employee is Terminated, but Termination Date is in the Future
This message is expected behavior for an employee who has given notice with a future termination date. The record will show this message on every sync run until the termination date has passed. Nothing will be written to HCSS for that employee in the meantime.
- If the future date is correct (for example, the employee gave advance notice), no action is needed.The record will sync on the next sync run once the termination date has passed.
- If the future date was entered by mistake, correct the termination date in the source system to the intended date.
- Run the sync again after the date has passed or been corrected.
- Confirm in the sync log that the employee row no longer shows this message and that the employee was added or updated in HCSS.
Once a terminated employee syncs successfully, the employee is written to HCSS as inactive. Active status in HCSS is set based on whether the employee's status is Terminated, so a terminated employee should appear as inactive in HCSS once the record is accepted.
Same-day termination dates are not considered "in the future"
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- You confirm the termination date is entered and in the past, but the message still appears after a fresh sync run.
- The employee's status and termination date look correct in the source system, but you cannot tell from the sync log which value the connector actually read.
Please Note
- The exact time-of-day and time zone carried on a "Termination Date" value as it arrives at this check is not established from this code. Because the future-date check compares full date and time (not date-only) against the current UTC moment, a termination date entered as "today" in the source system could still be treated as in the future or in the past depending on what time value the source system stores for that date. Entering a same-day termination date may or may not sync on the same day.