Before Arcoro sends any employee to Viewpoint Spectrum, it first loads a small set of reference data from Spectrum. Right now that reference data is the list of deduction and addon (fringe) codes that benefit and fringe amounts are checked against. If that setup step fails for any reason, the whole sync run stops immediately. Nothing is written to Spectrum in that run, not one employee, because this step happens before any employee is read or processed.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| One or more errors occurred in Employee preload for the Viewpoint Spectrum Provider. Review the logs, correct the data issue and run the Sync again. | Arcoro to Spectrum (write) | Any exception is thrown while Arcoro loads its Employee preload data, before any employee is processed. This is a generic wrapper message. Today the only thing this setup step loads is the deduction and addon code lookup below, so this message and the deduction/addon codes message always describe the same failure in the same run. | Sync stopped | Work the fix for Failed to retrieve Deduction/Addon codes from Spectrum below. That is the current cause of this message. |
| Failed to retrieve Deduction/Addon codes from Spectrum. Please check the Connector configuration and try again. | Arcoro to Spectrum (write) | The call to Spectrum for deduction and addon (fringe) codes fails, and only when the Employees entity has the Deduction Benefits scope or the Fringe Benefits scope turned on for that sync step. If neither scope is on, this lookup is never called and cannot fail. | Sync stopped | Confirm the connector’s Spectrum Authorization ID and Company Codes are correct and still authorized for this lookup on the Spectrum side, then re-run. |
Confirming the Error
- In Sync History, open the sync execution reported.
- Open the step for the Viewpoint Spectrum connector.
- Check the Added, Updated, and Unchanged counts for every entity in that step. This preload step runs before any employee is read, so a failure here leaves every entity at zero Added, zero Updated, and zero Unchanged for the whole run. A non-zero Failures count paired with all-zero processed counts is the signature of this family.
- Open the Failures detail for the step and match on the fixed part of the sentence: “One or more errors occurred in Employee preload for the Viewpoint Spectrum Provider”.
- In the sync log that Sync History shows you, this generic preload sentence is the only text you will see for this family, even when the deduction and addon code lookup is the cause.
- Two Information-level setup messages normally appear for this step, one announcing that Employee preload started and one announcing that it finished. If you see the start message but not the finish message for that step, and the run ended in Failure, that reliably means this preload step is what failed.
Resolving the Error
- Confirm the sync step actually needs this lookup: it only runs when the Employees entity has the Deduction Benefits scope or the Fringe Benefits scope enabled for that step. If neither is enabled, this is not the cause and you should escalate for a different reason.
- In Arcoro, open the connector’s configuration page and check the Spectrum Authorization ID and Company Codes fields for the Viewpoint Spectrum connector. Confirm they are populated and match what your Spectrum administrator expects for this Spectrum company.
- Confirm the Authorization ID still has permission to retrieve deduction and addon codes in Spectrum. A passing connection test on this connector does not confirm this permission, because the connection test only validates the Authorization ID and, if enabled, the SFTP destination. It does not call the deduction and addon code lookup itself.
- If the codes cannot be restored quickly and you need the rest of the Employee sync to run, the Deduction Benefits and Fringe Benefits scopes can be turned off for the Employees entity on that sync step so this lookup is skipped. This is a temporary workaround, not a fix, and benefit and fringe data will not sync while those scopes are off.
- Re-run the sync and confirm the Employee step now shows Added, Updated, or Unchanged counts greater than zero, with no new Failures entry for this step.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The connector configuration fields are already correct and you confirm Spectrum-side permissions are unchanged, but the failure persists.
- The connection test for this connector passes, since that only proves authentication and SFTP access, not that the deduction and addon code lookup itself will succeed.
- You need to know whether the specific cause was the deduction and addon code lookup or some other preload failure. The Sync History screen only ever shows the generic preload sentence; confirming the specific cause requires engineering to check Arcoro’s internal application log for that run.
- The Failures count is non-zero but Added, Updated, and Unchanged are not all zero for the step, since that does not match the pattern described in this article and may be a different failure.