Module Navigation

Sage Intacct with Arcoro Time Troubleshooting: Preload and Lookup Data Setup

Before Arcoro Time reads or writes any record for an entity, it first loads reference data it needs for that step, for example locations, cost codes, pay groups, or the existing records it will match against. This setup work is called preload. If preload cannot finish, the whole step for that entity stops immediately, before a single record is processed. The message you see is a summary that only says preload failed for that entity; it does not, by itself, say why. For most of these entities, look for a more specific detail message logged in the run just before the summary. Only two entities in this family, Time Record and Expense, have a detail message that is currently known to appear before the summary, and even then it is not guaranteed on every failure.

Error Messages

Message textDirectionOccurs whenOutcomeFix
One or more errors occurred in Employee PreLoad for the Arcoro Time Provider. Review the logs, correct the data issue and run the Sync again.Read - Arcoro Time to ArcoroEmployee entity read step. Setup loads locations, and when Hub is connected, Business Units and Hub employees. No condition in this setup currently logs a distinguishing detail message before this failure.Sync stopped: the Employee step ends before any employee is read.Re-run the sync; if the Employee step fails again with no detail line above it, escalate with the log excerpt.
One or more errors occurred in Employee PreLoad for the Arcoro Time Provider. Review the logs, correct the data issue and run the Sync again.Read - Arcoro Time to ArcoroTime Off Balance entity read step (a different service from the row above, sharing the same text). Setup loads the employee list, time off plan names, pay groups, and when Hub is connected, Hub employees. No condition in this setup currently logs a distinguishing detail message before this failure.Sync stopped: the Time Off Balance step ends before any balance is read.Re-run the sync; if the Time Off Balance step fails again with no detail line above it, escalate with the log excerpt.
One or more errors occurred in Contractor PreLoad for the Arcoro Time Provider. Review the logs, correct the data issue and run the Sync again.Read - Arcoro Time to ArcoroContractor entity read step. Setup loads locations, and when Hub is connected, Business Units and Hub employees. No condition in this setup currently logs a distinguishing detail message before this failure.Sync stopped: the Contractor step ends before any contractor is read.Re-run the sync; if the Contractor step fails again with no detail line above it, escalate with the log excerpt.
One or more errors occurred in Time Record PreLoad for the Arcoro Time Provider. Review the logs, correct the data issue and run the Sync again.Read - Arcoro Time to ArcoroTime Record entity read step. Setup loads locations, cost codes, jobs, pay periods, plan names, pay groups, rate codes, employees, contractors, and when Hub is connected, Business Units, Hub employees and Hub jobs. Fires either after an employee or contractor duplicate Arcoro ID detail line, or with no detail line at all if any other part of this setup runs into an unexpected problem. This is the one message in the family where an unrelated, unlogged setup problem can also produce this exact text.Sync stopped: the Time Record step ends before any time record is read.Look for a duplicate Arcoro ID detail line directly above; if there is none, escalate with the log excerpt.
One or more errors occurred in Timeoff Plan PreLoad for the Arcoro Time Provider. Review the logs, correct the data issue and run the Sync again.Read - Arcoro Time to ArcoroTime Off Plan entity read step. Setup loads locations and cost codes. No condition in this setup currently logs a distinguishing detail message before this failure.Sync stopped: the Time Off Plan step ends before any plan is read.Re-run the sync; if the Time Off Plan step fails again with no detail line above it, escalate with the log excerpt.
One or more errors occurred in Equipment PreLoad for the Arcoro Time Provider. Review the logs, correct the data issue and run the Sync again.Read - Arcoro Time to ArcoroEquipment entity read step, the side that brings equipment records out of Arcoro Time. Setup loads locations and equipment types. No condition in this setup currently logs a distinguishing detail message before this failure. Shares its exact text with the write-side Equipment message below; tell them apart by whether the failing step is the read side or the write side of that sync run.Sync stopped: the Equipment read step ends before any equipment record is read.Re-run the sync; if the Equipment read step fails again with no detail line above it, escalate with the log excerpt.
One or more errors occurred in Expense PreLoad for the Arcoro Time Provider. Review the logs, correct the data issue and run the Sync again.Read - Arcoro Time to ArcoroExpense entity read step. Setup loads expense types, employees, contractors, pay groups, rate codes, and when Hub is connected, Hub employees. Currently the only known way to trigger this is an employee or contractor duplicate Arcoro ID, which always logs a detail line first.Sync stopped: the Expense step ends before any expense is read.Read the duplicate Arcoro ID detail line directly above; it always names the record to correct.
One or more errors occurred in Union PreLoad for the Arcoro Time Provider. Review the logs, correct the data issue and run the Sync again.Write - source system into Arcoro TimeUnion entity write step. Setup loads every existing Arcoro Time union to match against. No condition in this setup currently logs a distinguishing detail message before this failure.Sync stopped: the Union step ends before any union is written.Re-run the sync; if the Union step fails again with no detail line above it, escalate with the log excerpt.
One or more errors occurred in Equipment Type PreLoad for the Arcoro Time Provider. Review the logs, correct the data issue and run the Sync again.Write - source system into Arcoro TimeEquipment Type entity write step. Setup loads every existing Arcoro Time equipment type to match against. No condition in this setup currently logs a distinguishing detail message before this failure.Sync stopped: the Equipment Type step ends before any equipment type is written.Re-run the sync; if the Equipment Type step fails again with no detail line above it, escalate with the log excerpt.
One or more errors occurred in Department PreLoad for the Arcoro Time Provider. Review the logs, correct the data issue and run the Sync again.Write - source system into Arcoro TimeDepartment entity write step. Setup loads every existing Arcoro Time department to match against. No condition in this setup currently logs a distinguishing detail message before this failure.Sync stopped: the Department step ends before any department is written.Re-run the sync; if the Department step fails again with no detail line above it, escalate with the log excerpt.
One or more errors occurred in Cost Type PreLoad for the Arcoro Time Provider. Review the logs, correct the data issue and run the Sync again.Write - source system into Arcoro TimeCost Type entity write step. Setup loads every existing Arcoro Time cost type to match against. No condition in this setup currently logs a distinguishing detail message before this failure.Sync stopped: the Cost Type step ends before any cost type is written.Re-run the sync; if the Cost Type step fails again with no detail line above it, escalate with the log excerpt.
One or more errors occurred in Equipment PreLoad for the Arcoro Time Provider. Review the logs, correct the data issue and run the Sync again.Write - source system into Arcoro TimeEquipment entity write step, the side that writes equipment records into Arcoro Time. Setup loads every existing Arcoro Time equipment record and every active equipment type to match against. No condition in this setup currently logs a distinguishing detail message before this failure. Shares its exact text with the read-side Equipment message above; tell them apart by whether the failing step is the read side or the write side of that sync run.Sync stopped: the Equipment write step ends before any equipment record is written.Re-run the sync; if the Equipment write step fails again with no detail line above it, escalate with the log excerpt.
More than one Employee has the same Arcoro ID of '[Arcoro person ID]'. Contact support to correct your data and execute the Sync again.Read - Arcoro Time to ArcoroLogged once per extra employee record that Arcoro Time returns carrying an Arcoro person ID already seen on another employee record in that same run. Appears just before Time Record PreLoad or Expense PreLoad fails; it is the detail line those two summaries can carry.Sync stopped: logged as its own line, then the whole Time Record or Expense step halts.Contact support to correct the duplicate Arcoro ID on the named employee records.
More than one Contractor has the same Arcoro ID of '[Arcoro person ID]'. Contact support to correct your data and execute the Sync again.Read - Arcoro Time to ArcoroLogged once per extra contractor record that Arcoro Time returns carrying an Arcoro person ID already seen on another contractor record in that same run. Appears just before Time Record PreLoad or Expense PreLoad fails; it is the detail line those two summaries can carry.Sync stopped: logged as its own line, then the whole Time Record or Expense step halts.Contact support to correct the duplicate Arcoro ID on the named contractor records.

Confirming the Error

  1. Open Sync History for the run and find the row for the entity named in the message: Employee, Contractor, Time Record, Time Off Plan, Time Off Balance, Equipment, Union, Equipment Type, Department, or Cost Type.
  2. Match on the fixed wording of the message, not on any value shown in quotes or brackets, since several of these messages are worded identically across entities.
  3. Check the Failures column for that entity. A preload failure logs at Failure, not Error, so this is where the summary message itself will be counted.
  4. Check Added, Updated, and Unchanged for that entity. All three will be zero, because the step stopped before any record was read or written.
  5. Check the Errors column. It will be zero unless this is the Time Record or Expense entity and an Arcoro ID duplicate was found, in which case Errors shows one entry per duplicate record.
  6. Open the detailed log for that entity and look at the line immediately above the failure. If it is one of the two Arcoro ID duplicate messages, note the Arcoro person ID it names. If the line above is unrelated, or there is no line above it at all, there is nothing more specific in this run's log to go on.
  7. If the message text is the Equipment PreLoad text, confirm from the sync step configuration whether the failing side is the read side (Arcoro Time as source) or the write side (Arcoro Time as destination) before choosing a fix.

Resolving the Error

When a Duplicate Arcoro ID Is Named

  1. Confirm the message is one of the two Arcoro ID duplicate messages and note the Arcoro person ID and whether it is an Employee or a Contractor record.
  2. This condition means Arcoro Time itself is returning more than one Employee or Contractor record tagged with that same Arcoro person ID. Correcting it is a data correction inside Arcoro Time on the record's Arcoro ID assignment, not something Tier 1 can change directly.
  3. Follow the message's own instruction and contact support to have the duplicate corrected.
  4. Once corrected, re-run the sync and confirm the affected entity's Sync History row now shows Added, Updated, or Unchanged counts instead of a Failure.

When No Detail Message Names a Record

  1. This covers every PreLoad summary in this article except the two cases above. There is no specific record to correct.
  2. Re-run the sync once.
  3. If it fails again with the same summary message and still no detail line above it, do not attempt to find or correct an individual record. Escalate instead, with the sync ID, the entity, the exact time of the failure, and the surrounding log lines.
  4. Confirm resolution the same way: re-run the sync and check that the entity's Sync History row shows Added, Updated, or Unchanged counts instead of a Failure.

When to Escalate

If any of the following occur, you may need to reach out to Arcoro support for additional assistance.

  • The failure is a PreLoad summary message with no Arcoro ID duplicate line, or any other detail line, directly above it in the log. This applies to every message in this article except the two Arcoro ID duplicate messages themselves.
  • The message is Time Record PreLoad or Expense PreLoad and the log shows no Arcoro ID duplicate line above it, since that means an unnamed problem interrupted setup rather than a specific bad record.
  • A duplicate Arcoro ID message keeps recurring on repeat sync attempts after support has been asked to correct it.
  • The Equipment PreLoad text appears and it is unclear from the sync step configuration whether the read side or the write side failed.
Was this article helpful?
0 out of 0 found this helpful