Everything after "Description:" in this message is passthrough text from Viewpoint Spectrum. Arcoro is not generating that wording; it is just wrapping whatever error code, column name, and description Spectrum sent back and writing it to the sync log. This message appears while Arcoro is asking Spectrum for the list of deduction and fringe (addon) codes it needs before it can write an employee's benefit deductions or fringe benefits. It is not logged while the employee record itself is being written.
Because the description comes from Spectrum, it may not match the wording of any other Arcoro article.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Viewpoint Spectrum error response. Error Code: [Spectrum error code]; Column: [column name]; Description: [Spectrum description] | Write (Arcoro to Spectrum) | Arcoro is retrieving the deduction and fringe (addon) code list from Spectrum before writing benefit deductions or fringe benefits, and Spectrum returned a code row with an error code other than blank/none for it. | Logging only. The code row is still included in Arcoro's lookup list; nothing is skipped by this message on its own. | Capture the Error Code, Column, and Description exactly as logged and escalate. This text is written by Spectrum, not Arcoro. |
Reading the Message
The sentence has three parts that come from Spectrum's response, in this order.
| Part of the message | What it contains | Where it comes from |
|---|---|---|
| Error Code | A single-letter code Spectrum assigned to this deduction/addon code row. | Spectrum's response to the deduction and fringe code lookup. |
| Column | The name of the field or column on the Spectrum side that the error relates to. | Spectrum's response. |
| Description | Free text Spectrum wrote describing the problem with that code or column. | Spectrum's response. This text is not defined by Arcoro and will vary by account and code. |
Severity Depends on the Code Spectrum Returned
The exact same sentence is logged at a different severity depending on the Error Code value Spectrum sent back. A code row with no error code, or an error code of None, is not logged at all.
| Response code | Logged as | What it means for the sync |
|---|---|---|
| None | Not logged at all | No error on this code row. This is the normal, healthy case and is filtered out before this message is ever produced. |
| Warning | Warning | Spectrum flagged something about this code row, but it is not treated as blocking. |
| Invalid | Error | Spectrum reports an invalid value on this code row. |
| Abort | Error | Spectrum reports a security or authorization problem with the request for this code row. |
| Missing | Error | Spectrum reports required information is missing for this code row. |
| Successful | Information | Logged for visibility only. Not an error condition. |
| Good | Information | Spectrum sent back informational text for this code row. Not an error condition. |
Confirming the Error
- Open the sync history entry for the run in question and find the employee entity's row.
- Check the Errors, Warnings, and Information columns for the run. Because the same sentence can appear under any of the three depending on the Spectrum code, do not assume it is only under Errors.
- Open the detail log for whichever column has entries and look for a line that starts with "Viewpoint Spectrum error response. Error Code:". The Error Code, Column, and Description values after that fixed lead-in will vary row to row; match on the fixed part of the sentence.
- Note the Added, Updated, and Unchanged counts for the employee entity on the same run. If those counts look normal for the batch, this message did not by itself block employee records from syncing.
- If deduction or fringe benefit records for affected employees are missing or showing as errors, check whether Errors also contains messages about individual benefit deduction or fringe benefit records; those come from a separate check and have their own article.
Resolving the Error
- Copy the full message text exactly as logged, including the Error Code, Column, and Description.
- Confirm the connector configuration used for this sync, since this message occurs during the deduction and fringe code lookup that runs before benefit deductions or fringe benefits are written.
- Do not attempt to edit source data in response to this message alone. The description is generated by Spectrum, not by Arcoro, and does not map to a known Arcoro field.
- Escalate with the captured text so engineering or the Spectrum administrator can interpret the specific Error Code, Column, and Description.
- Once the underlying Spectrum-side issue is resolved, re-run the sync and confirm this message no longer appears for the same code, and that any related benefit deduction or fringe benefit records for affected employees now appear in Added or Updated rather than Errors.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- Always for this message. Escalate any time it appears at Error or Warning severity.
- Before escalating, copy the exact Error Code, Column, and Description values from the log line.
- Note whether it was logged as an Error, a Warning, or Information for this run.
- Note the company code and, if known, which deduction or fringe (addon) code the row relates to.
- Note whether any employee's benefit deduction or fringe benefit records failed on the same run, since that may be a separate, related issue.