These eight messages all come from Arcoro Time read services, meaning data is flowing out of Arcoro Time and into the Arcoro sync platform. Because Arcoro Time is the source of truth here, the fix for almost every one of these lives inside Arcoro Time itself, not in the destination system.
Most of these messages describe a single time record, expense, expense type, or plan balance that could not be mapped, while the rest of that employee's data continues to sync normally. A smaller number affect the whole employee record or come directly from Arcoro Time's own backend process rather than from the sync platform.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| The Time Record does not contain a valid ArcoroPersonId and will not be synced. Contact support to resolve this issue. | Read: Arcoro Time to Arcoro (Time Record and Expense entities) | The employee or contractor referenced by the time record or expense could not be resolved in the preloaded employee or contractor list for this connector. | Whole record skipped. The employee's other time or expense records are unaffected. | Escalate to support. Do not attempt to fix in Arcoro Time first. |
| One or more Time Records do not have either a start punch or a stop punch and are not valid time records. These records will not be Synced. Correct the data in Arcoro Time and execute the Sync again. | Read: Arcoro Time to Arcoro (Time Record entity) | Among the employee's time records for the pay period, at least one record of Type "TimeRecord" is missing its start punch id, its stop punch id, its start date and time, or its end date and time. This check only applies to the "TimeRecord" type, not to MealBreak, TimeOff, Timesheet, or TimeStamp records. | Logged once for the employee's whole batch. Only the specific incomplete "TimeRecord" entries are removed; every other record for that employee, including complete TimeRecord entries and all other record types, still syncs. | Complete the missing punch in Arcoro Time, then run the sync again. |
| One or more Time Records has an unsupported Type and those records will not be synced. The Arcoro Time Provider does not support the following Types: AdditiveCallout, AdditiveOvertimeRounding, NegativeAdvancedAutoLunch, NegativeOvertimeRounding, Unknown. Change the record to a supported Type and execute the Sync again. | Read: Arcoro Time to Arcoro (Time Record entity) | Among the employee's time records, at least one record has a Type this connector never supports. The message text names five of those types, but the underlying check actually excludes nine: AdditiveCallout, AdditiveAutoLunch, AdditiveOvertimeRounding, AdvancedAutoLunch, AutoLunch, EditedAutoLunch, NegativeAdvancedAutoLunch, NegativeOvertimeRounding, and Unknown. Match on the fixed wording of the message, not on the type list. | Logged once for the employee's whole batch. Only the records with one of these Types are removed; every other record for that employee still syncs. | These record Types cannot be changed to a supported one in this article's scope. Escalate if this data needs to be synced. |
| A time record with an unsupported type of [record type] was encountered. This record will not be processed. | Read: Arcoro Time to Arcoro (Time Record entity) | A single time record's Type value is not one of the five types this reader knows how to build a record label for (MealBreak, TimeOff, TimeRecord, Timesheet, TimeStamp), and it was also not one of the nine Types already filtered out by the "unsupported Type" check above. This is a narrower, separate check for a Type value Arcoro Time returned that neither list expected. | Only the one offending record is skipped. The rest of the employee's records still sync. This is a different, rarer condition than the "unsupported Type" message above; do not treat the two as the same issue. | Escalate to support with the record Type shown in [record type]. |
| The auto lunch rollup process has failed: WorkDate: [work date], FriendlyIdentifier: [employee name or raw error text], [employee id or raw error text] | Read: Arcoro Time to Arcoro (Time Record entity, endpoint-level) | Arcoro Time's own auto lunch rollup process returned an error for a date range queried during the sync. This text is reformatted with the employee's name and Employee Id only when both of the following are true: the error text matches an expected pattern with a WorkDate and an ArcoroPersonId, and that ArcoroPersonId is found in the preloaded employee list. If either condition fails, the agent instead sees the raw, unformatted error text exactly as Arcoro Time returned it. | Logged as an entity-level error for the connector, not attached to any single employee row. The sync continues for the rest of the date range and all other employees. | This text originates entirely in Arcoro Time, not in the sync platform. Always escalate. |
| The Employee Plan with Id '[plan employee id]' references a Plan that could not be found. The record will not be Synced. Correct the data in Arcoro Time and run the Sync again. | Read: Arcoro Time to Arcoro (Employee Time Off Balance entity) | One of the employee's PTO plan enrollments references a Plan Id that no longer exists in Arcoro Time's list of plans. | Only that one plan balance entry is skipped. The employee's other plan balances still sync. Despite the name ending in "Warning," this is logged and counted as an Error in the sync log. | Review the employee's PTO plan assignment in Arcoro Time and either restore the plan or reassign the employee to a valid plan, then run the sync again. |
| An Expense Type with Id: '[expense type id]' does not have a Name. This field is required and the record will not be Synced. Modify the data in Arcoro Time to make each record have a unique Name and execute the Sync again. | Read: Arcoro Time to Arcoro (Expense Type entity) | An Expense Type record has a blank or whitespace-only Name. | Whole Expense Type record skipped. | Add a Name to the Expense Type in Arcoro Time, then run the sync again. |
| An Expense Type with Name: '[expense type name]' has already been read. This field must be unique and the record will not be Synced. Modify the data in Arcoro Time to make each record have a unique Name and execute the Sync again. | Read: Arcoro Time to Arcoro (Expense Type entity) | Two or more Expense Types returned in this same sync run share the same Name, compared without regard to letter case. The comparison is only against names already read earlier in this run, not against any Expense Type already synced to the destination. | Whole Expense Type record skipped for every occurrence after the first one read. | Rename the duplicate Expense Type in Arcoro Time so every Name is unique, then run the sync again. |
Confirming the Error
- Open the sync's execution in Sync History and locate the Time Record, Expense, Expense Type, or Employee Time Off Balance entity row for this run.
- Compare the Errors, Warnings, Information, Failures, Added, Updated, and Unchanged columns for that entity against what is reported missing.
- Because most of these messages drop only individual records or plan balances, the employee itself will usually still show up in Added, Updated, or Unchanged. A nonzero Errors count with the employee still present in one of those columns is expected and does not mean the whole employee failed.
- Open the entity's detail log for the affected employee and find the message text. Match on the fixed wording described in this article, not on the values inside quotes or brackets, since those change per employee, date, or record.
- For the auto lunch rollup message, check whether the log line contains an employee name and Employee Id or looks like a raw, differently worded error. Either form is Arcoro Time's own text passed through unchanged.
- For the Employee Plan message, confirm it is logged under Errors. It is counted as an error even though its wording is advisory, so an Errors count of one is expected here and is not a logging fault.
Resolving the Error
Missing or Unresolved Person (ArcoroPersonId)
- Do not attempt a fix in Arcoro Time. Escalate this message to support with the Sync History detail log entry.
Incomplete Time Records and Unsupported Record Types
- In Arcoro Time, open the employee's time card for the pay period referenced in the sync log.
- For the incomplete time record message, find the entry missing a start or stop punch and add the missing punch.
- For the unsupported Type message listing the nine excluded Types, these records cannot be changed to a supported Type from this article; escalate if the data needs to be synced.
- For the single-record "unsupported type of [record type]" message, escalate to support with the record Type value from the message, since this indicates a Type Arcoro Time returned that the connector does not otherwise recognize at all.
- Run the sync again and confirm the corrected record now appears in Added or Updated for that employee.
Auto Lunch Rollup Failure
- Escalate to support. This message is generated entirely inside Arcoro Time's own backend process, not by the sync platform, so tier 1 cannot resolve it directly.
Employee Plan References a Missing Plan
- In Arcoro Time, open Company Setup and review the list of active PTO Plans.
- Either restore the missing Plan or reassign the employee's plan enrollment to an existing Plan.
- Run the sync again and confirm the employee's Time Off Balances now include the corrected plan.
Expense Type Missing a Name or Duplicated
- In Arcoro Time, open the Expense Types list under Company Setup.
- For a missing Name, add one to the Expense Type.
- For a duplicate Name, rename one of the conflicting Expense Types so every Name is unique. Remember the duplicate check only looks at Expense Types returned in the same run, so two Expense Types that look identical may still need distinct Names even if only one currently causes an error.
- Run the sync again and confirm both Expense Types now appear in Added or Updated.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The Time Record does not contain a valid ArcoroPersonId message. The resource text itself says to contact support; do not attempt a fix in Arcoro Time.
- The auto lunch rollup message. Its text is passthrough from Arcoro Time's own backend process, so tier 1 has no data screen to correct.
- The single-record unsupported type message, when the Type named in the message is unfamiliar or not documented anywhere you can change.
- Any of these messages recurring across multiple sync runs after you have made the suggested correction in Arcoro Time.