Skip to content

Error Reference: Validation Errors

This page lists every validation error message the application can display, grouped by validation mode. Use the exact error text to find the entry that matches what you see on screen or in the log.

All Modes -- General

"Reject All mode - automatic rejection"

  • What it means: The validation mode is set to "RejectAll," which is a testing mode that automatically rejects every case.
  • Common causes: 1. The validation mode was accidentally set to RejectAll.
  • Resolution: Change the validation mode to the correct mode for this site.
  • When to escalate: Never -- this is a configuration issue.

AV50 Mode

"Found {count} valid barcodes, required {minimum}"

  • What it means: The camera found fewer valid barcodes than the configured minimum requirement in single-camera mode.
  • Common causes: 1. Barcode on the case is missing or damaged. 2. Camera cannot read the barcode (print quality, positioning, lighting). 3. Camera returned NOREAD.
  • Resolution: 1. Check the barcode label on the case. 2. Reposition the case in front of the camera. 3. If the camera consistently cannot read, check camera focus and settings.
  • When to escalate: If the camera is connected but never reads any barcodes.

"{cameraName} has {count} valid barcodes, required {minimum}"

  • What it means: A specific camera (Front or Side) found fewer valid barcodes than required in multi-camera mode.
  • Common causes: Same as above, but specific to one camera.
  • Resolution: Check the barcode label on the side facing the named camera.
  • When to escalate: If one camera consistently fails while the other works.

"Both cameras failed: Front - {reason}; Side - {reason}"

  • What it means: In "Both" camera mode, both the Front and Side cameras failed to read enough barcodes.
  • Common causes: 1. Case has no barcodes on either side. 2. Both cameras are malfunctioning.
  • Resolution: Check barcode labels on both sides. Check both cameras in Diagnostics.
  • When to escalate: If both cameras fail consistently.

CargillRfid and Chipotle Modes

"Missing required barcodes (2D and UCC-128)"

  • What it means: The camera returned fewer than 2 barcodes. Both a 2D barcode (DataMatrix or QR) and a UCC-128 barcode are required.
  • Common causes: 1. Camera only read one barcode. 2. Case label is missing one of the two barcodes. 3. Camera triggered before the case was fully in position.
  • Resolution: 1. Check that the case label has both a DataMatrix and a UCC-128 barcode. 2. Check camera positioning and timing.
  • When to escalate: If the camera consistently reads only one barcode.

"Missing 2D barcode"

  • What it means: The camera read barcodes, but none of them were a DataMatrix or QR type.
  • Common causes: 1. The 2D barcode is damaged or not present on the label. 2. Camera could not decode the 2D barcode (print quality issue).
  • Resolution: Check the physical label for a clear DataMatrix barcode.
  • When to escalate: If the DataMatrix is clearly present and readable but the camera cannot decode it.

"Missing UCC-128 barcode"

  • What it means: The camera read barcodes, but none of them were a Code128 or UCC-128 type.
  • Common causes: 1. The UCC-128 barcode is damaged or not present on the label. 2. Camera could not decode the UCC-128 barcode.
  • Resolution: Check the physical label for a clear UCC-128 barcode.
  • When to escalate: If the barcode is clearly present but the camera cannot decode it.

"Missing expected production data"

  • What it means: No production data has been received from the Matthews TCP interface.
  • Common causes: 1. Matthews system is not sending data. 2. Matthews interface is not enabled. 3. Firewall blocking port 60251. 4. IP filter rejecting the Matthews connection.
  • Resolution: 1. Check EnableMatthewsInterface is true in appsettings.json. 2. Verify the Matthews system is running and configured to send to this machine. 3. Check firewall rules for port 60251. 4. Check MatthewsAllowedIp setting.
  • When to escalate: If the Matthews system is confirmed sending but GateKeeper is not receiving.

"No matching RFID data"

  • What it means: The RFID tag for this case was not found in the tag cache. The 2D barcode EPC did not match any recently read RFID tags.
  • Common causes: 1. RFID tag is not present on the case. 2. RFID tag is not in the antenna read zone. 3. Tag passed through the read zone before the camera triggered (tag expired from cache -- default 17 second timeout). 4. RFID reader is disconnected.
  • Resolution: 1. Verify the case has an RFID tag. 2. Check RFID reader connection in Diagnostics. 3. Check RFID tag cache in Diagnostics for recent tags. 4. If tags expire too quickly, increase RFID.TagExpirationSeconds in appsettings.json.
  • When to escalate: If the RFID reader is connected, tags are being read, but validation still reports no match.

"Invalid GS1 barcode format: {parseError}"

  • What it means: The UCC-128 barcode was read but its content could not be parsed as a valid GS1 barcode.
  • Common causes: 1. Barcode is damaged and partially read. 2. Barcode was printed with incorrect content. 3. Barcode format does not follow GS1 standards.
  • Resolution: Check the physical barcode label. Compare the scanned data to what the label should contain. Contact the label printing team if the barcode content is wrong.
  • When to escalate: If the barcode appears correct but still fails parsing.

"Invalid GS1 barcode format"

  • What it means: The barcode was parsed but did not contain valid GS1 data (missing required fields like GTIN).
  • Common causes: Same as above.
  • Resolution: Same as above.

"GTIN mismatch: expected {expected}, found {found}"

  • What it means: The GTIN from the UCC-128 barcode does not match the GTIN from the Matthews production data.
  • Common causes: 1. Wrong product on the line. 2. Matthews sent the wrong GTIN. 3. Barcode printed with wrong GTIN.
  • Resolution: 1. Verify the correct product is on the line. 2. Check Matthews data. 3. Check barcode label.
  • When to escalate: If the GTIN values look correct but are being compared incorrectly.

"Expiration date mismatch: expected {expected}, found {found}"

  • What it means: The expiration date from the UCC-128 barcode does not match the expected date from production data, beyond the configured tolerance.
  • Common causes: 1. Barcode has wrong expiration date. 2. Matthews sent wrong date. 3. Tolerance setting is too strict.
  • Resolution: 1. Compare the dates shown in the error. 2. Check CargillRfid.ExpirationTolerance (or Chipotle.ExpirationTolerance) in appsettings.json. A value of 1 means plus or minus 1 day is acceptable.
  • When to escalate: If dates are within tolerance but still failing.

CargillSalt Mode

"No production data available - waiting for file import"

  • What it means: The NetworkFileImporter has not imported any file yet.
  • Common causes: 1. No import file in the configured directory. 2. NetworkFileImporter is not enabled.
  • Resolution: Check the import directory and the EnableNetworkFileImporter setting. See Data Import Issues.

"Invalid production data: missing GTIN"

  • What it means: The imported file was read but the GTIN column is empty.
  • Common causes: The source data file has an empty GTIN field.
  • Resolution: Check the import file content and contact the data provider.

"No barcode read from camera"

  • What it means: The Insight camera returned no barcode data (NOREAD).
  • Common causes: 1. Camera could not read the OCR text. 2. Case not in camera view. 3. Camera disconnected.
  • Resolution: Check camera connection and case positioning.

"Invalid barcode format - could not extract date from: {barcode}"

  • What it means: The barcode read by the camera is not in the expected format (PRODUCTCODE;PLANTCODE;DATE).
  • Common causes: 1. OCR read the wrong area of the label. 2. Label format changed.
  • Resolution: Check the OCR output and verify the label format matches the expected semicolon-delimited format.

"Expiration date mismatch: expected {expected}, camera read {actual}"

  • What it means: The OCR date from the camera does not match the expected expiration date from the import file.
  • Common causes: 1. Wrong date printed on the product. 2. Import file has wrong date.
  • Resolution: Compare the dates and check with the production team.

Teasdale Mode

"Missing expected production data"

  • What it means: No production data from the TeasdaleImporter. No job has been loaded.
  • Common causes: 1. No job file sent from DCOM. 2. Import file was rejected (missing fields). 3. TeasdaleImporter is not enabled.
  • Resolution: See Data Import Issues.

"Missing: {components}"

  • What it means: One or more required scan components are missing. The message lists what is missing (for example, "Missing: DataMatrix barcode, RFID tag").
  • Common causes: 1. Camera did not read a DataMatrix barcode. 2. Camera did not read a UCC-128 barcode. 3. RFID tag was not detected.
  • Resolution: Check which components are missing and troubleshoot that specific hardware.

"DataMatrix '{value}' does not match RFID '{epc}'"

  • What it means: The DataMatrix barcode value does not exactly match the RFID EPC.
  • Common causes: 1. RFID tag is from a different case (reading adjacent cases). 2. RFID tag was encoded incorrectly. 3. DataMatrix barcode was printed with wrong value.
  • Resolution: 1. Ensure only one case is in the RFID read zone. 2. Check RFID tag encoding. 3. Check label printing.

"GTIN mismatch: expected '{expected}', found '{found}'"

  • What it means: The GTIN from the UCC-128 barcode does not match the expected GTIN from the import file.
  • Resolution: Same as CargillRfid GTIN mismatch (see above).

"Lot number mismatch: expected '{expected}', found '{found}'"

  • What it means: The lot number from the UCC-128 barcode (AI 10) does not match the expected lot from the import file.
  • Common causes: 1. Labels printed with wrong lot number. 2. Import file has wrong lot. 3. Midnight rollover issue -- labels have the old day's lot number.
  • Resolution: 1. Check the lot on the physical label vs. the expected lot in the UI. 2. If this is after midnight, check if the midnight rollover occurred. See Handle Midnight Rollover.

"No date found in barcode (requires Pack Date AI 13, Best Before AI 15, or Expiration AI 17)"

  • What it means: The UCC-128 barcode does not contain any date Application Identifier.
  • Common causes: The barcode was printed without a date AI.
  • Resolution: Check the label template to ensure it includes AI 13, 15, or 17.

"Pack date mismatch: expected '{expected}', found '{found}'"

  • What it means: The Pack Date (AI 13) in the barcode does not match the expected production date.
  • Common causes: 1. Label printed with wrong date. 2. Midnight rollover shifted the expected date but labels still have the old date.
  • Resolution: Compare dates. Check midnight rollover status.

"Expiration date mismatch: expected '{expected}', found '{found}'"

  • What it means: The Expiration Date (AI 17) in the barcode does not match the expected expiration date.
  • Resolution: Same as Pack date mismatch.

Zfl Mode

"Missing expected EPC data from ZFL importer"

  • What it means: No ZPL data has been received by the ZflImporter.
  • Common causes: 1. Zebra printer not sending ZPL to GateKeeper. 2. Port 6101 blocked. 3. ZflImporter not running.
  • Resolution: Check that the printer is configured to send ZPL to the GateKeeper machine and port.

"Missing expected EPC in production data"

  • What it means: ZPL was received but no EPC could be parsed from it.
  • Common causes: ZPL data does not contain the expected EPC encoding.
  • Resolution: Check the ZPL template on the printer.
  • When to escalate: If the ZPL looks correct but cannot be parsed.

"No barcode data from FS40 scanner (0 barcodes)"

  • What it means: The FS40 scanner did not read any barcode.
  • Common causes: 1. Item not in scanner view. 2. Scanner disconnected. 3. Barcode too small or damaged.
  • Resolution: Check scanner connection and item positioning.

"EPC mismatch: expected '{expected}', scanned '{scanned}'"

  • What it means: The barcode scanned by the FS40 does not match the expected EPC from the ZPL data.
  • Common causes: 1. Wrong item scanned. 2. EPC queue is out of sync. 3. ZPL data is stale.
  • Resolution: 1. Verify the correct item is being scanned. 2. Use the "Clear Queue" button to discard stale EPCs.