These six errors all come from the outbound sync that writes Arcoro employee and union data to Viewpoint Spectrum. Spectrum enforces short field limits and a small set of valid codes for union, union class, and skill or work class data. When the data on the Arcoro record does not fit those rules, the connector logs an Error and, in most cases, does not send that record to Spectrum at all. Two of the six checks live on the Union entity, not the Employee entity, so the agent needs to look at the correct row in the sync log to find them.
One of the six behaves differently from the rest. It only blocks the single Union field on the employee from being sent. Everything else on that employee, including the rest of that same sync pass, still goes to Spectrum.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Workers Compensation Code is missing or in an invalid format. The Employee will not be Synced. The supported formats are either "Code-Description" or "Code". Correct the data in the source system and execute the Sync again. | Write (Arcoro to Spectrum) | Employee entity. The employee's Workers Compensation Code is blank after Arcoro parses it. This check runs before any other employee data is written, so it fires first if the employee has no code. | Record skipped. The whole employee is not written to Spectrum for this sync. | Add a valid Workers Compensation Code to the employee record in Arcoro, then rerun the sync. |
| Union code is required. The record will not be Synced. Correct the data in the source system and execute the Sync again. | Write (Arcoro to Spectrum) | Union entity. The Union's code is blank after Arcoro parses it. This check runs before any field on the Union is written. | Record skipped. The whole Union record is not written to Spectrum. | Add a code to the Union record in Arcoro, then rerun the sync. |
| Union code exceeds the Spectrum maximum length of 10 characters and will not be synced. | Write (Arcoro to Spectrum) | Union entity. The Union's code is longer than 10 characters. Same pre-write check as the row above, same entity. | Record skipped. The whole Union record is not written to Spectrum. | Shorten the Union code to 10 characters or fewer in Arcoro, then rerun the sync. |
| Union [union code] is not a valid union for the following employees. The employee will be synced without this data. Please correct and execute the sync again to correct this. | Write (Arcoro to Spectrum) | Employee entity. Despite the wording, this is not a lookup against your union list. It fires only when the employee's Union code is longer than 10 characters. A short code that does not exist in Spectrum will not trigger this message. | Field skipped only. The Union field is left off this employee. Every other field, including the rest of the sync, still goes through. | Shorten the employee's Union code to 10 characters or fewer in Arcoro, then rerun the sync. |
| The Union Class [union class value] exceeds the maximum length of [10] characters supported by Spectrum. Correct the data in the source system and run the sync again. | Write (Arcoro to Spectrum) | Employee entity. The employee's Union Class value is longer than 10 characters. | Record skipped. The connector still attempts to write every other field on the employee and logs those attempts, but the final send to Spectrum for that employee is blocked because of this one field. | Shorten the employee's Union Class value to 10 characters or fewer in Arcoro, then rerun the sync. |
| Write to Spectrum: The employee record will not be synced due to Skill - Work Class (UDFL15) value '[skill/work class value]' is invalid. The only valid options are Journeyman, Apprentice, or Trainee. | Write (Arcoro to Spectrum) | Employee entity. The first letter of the employee's Skill - Work Class value does not match one of the codes for Journeyman, Apprentice, or Trainee. | Record skipped. Same behavior as the Union Class row above: other fields are still attempted and logged, but the employee is not sent to Spectrum. | Set the employee's Skill - Work Class value to Journeyman, Apprentice, or Trainee in Arcoro, then rerun the sync. |
Confirming the Error
- Open the Sync History screen and find the sync execution in question.
- Open the step for the Viewpoint Spectrum connector inside that execution.
- This family involves two different entities. Check the row for the Employees entity and, separately, the row for the Unions entity. A "missing union" could show up on either row depending on which of the six checks fired.
- Look at the Errors column for each entity row. A non-zero count means at least one of these validations logged an Error for that entity during this run.
- A non-zero Failures count is a different thing for this family. Failures are tracked separately from Errors. None of these six messages populate the Failures count, only the Errors count. Do not treat a clean Failures count as proof these checks passed; check Errors instead.
- Open the Errors detail for the entity and match the fixed part of the sentence, for example "is not a valid union for the following employees" or "exceeds the maximum length of". Do not match on the quoted code or value, since that is specific to one employee or union.
- Note whether the affected entity row also shows a non-zero Added or Updated count. For the Union code checks, the Workers Compensation check, and the Union Class and Skill - Work Class checks, an affected record will not appear as Added or Updated because the whole record was skipped. For the Union-is-too-long-on-the-employee message, the employee can still show as Added or Updated even with the Error present, because only the Union field was left off.
Resolving the Error
Workers Compensation Code Missing or Invalid
- In Arcoro, open the employee record and add or correct the Workers Compensation Code field.
- Confirm the value is in the "Code" or "Code-Description" format Arcoro expects.
- Rerun the sync and confirm the employee now appears as Added or Updated with no Error for this employee.
Union Code Missing or Too Long (Union Entity)
- In Arcoro, open the Union record and add a code, or shorten the existing code to 10 characters or fewer.
- Rerun the sync and confirm the Union record now appears as Added or Updated on the Unions entity row.
Employee Union Code Too Long
- In Arcoro, open the employee record and shorten the Union value to 10 characters or fewer.
- Rerun the sync. The employee record itself should already have been syncing; confirm the Error for this employee is gone and that the Union field is now present on the Spectrum side.
Union Class Too Long, or Skill - Work Class Invalid
- In Arcoro, open the employee record.
- For a Union Class length issue, shorten the Union Class value to 10 characters or fewer.
- For a Skill - Work Class issue, set the value to Journeyman, Apprentice, or Trainee.
- Rerun the sync and confirm the employee now appears as Added or Updated with no Error for this employee.
If the entity row also shows a Warning about a wage code (union class) assigned without a union, that is a separate, lower-severity message. It is not one of the six errors covered in this article, but if you have both an Error and that Warning on the same employee, resolving the Union data usually clears both.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- You believe the union code on the employee is a real, active union in Spectrum and is 10 characters or fewer, but the message still reads "is not a valid union." The message text describes a validity lookup, but the actual check only tests the length of the code. If the code is short and the Error still appears, escalate rather than continuing to troubleshoot union validity, since the wording does not match what the connector is actually checking.
- The Union Class or Skill - Work Class Error persists after the value looks correct and short enough in Arcoro. This may indicate the value is not refreshing before the sync runs.
- Any Failures count on the Employees or Unions entity row for this connector. Failures are a different, more serious category than the Errors covered here and are outside the scope of this article.
- You need a code value added to Spectrum's own list of valid codes; support cannot make changes inside your Spectrum system.