Skip to content

Error Reference: Export Errors

This page lists error messages from the Mojix, MWE, and AIS export services.

Mojix Export Errors

"[MOJIX-EXPORT] Mojix submission {fileName} failed - retry count: {count}/{max}"

  • What it means: An export submission to the Mojix API failed. The system will retry automatically.
  • Common causes: 1. Mojix server is temporarily unreachable. 2. Network issue. 3. Mojix server returned an error.
  • Resolution: Check the next log lines for the HTTP status code and error details. The system will retry up to the maximum retry count. No immediate action needed unless retries are exhausted.

"[MOJIX-EXPORT] Submission failure details - StatusCode: {code}, Error: {message}"

  • What it means: Details about why the Mojix submission failed.
  • Common causes: Depends on the status code:
Status Code Meaning Resolution
401 Unauthorized Check Mojix credentials in appsettings.json
403 Forbidden Machine IP may not be whitelisted on Mojix server
404 Not Found MojixEndpointUrl path is wrong -- verify with integration partner
500 Server Error Mojix server issue -- contact integration partner
503 Service Unavailable Mojix server is down -- wait or contact integration partner
0 or Connection Refused Cannot connect Check network connectivity to Mojix endpoint

"[MOJIX-EXPORT] Mojix submission {fileName} exceeded maximum retries ({max}) - moving to error folder"

  • What it means: All retry attempts have been exhausted. The submission file has been moved to the error folder.
  • Common causes: The Mojix server has been unreachable for an extended period, or there is a persistent error.
  • Resolution: 1. Check C:\gatekeeper\conveyor\data\ais\error\ for the failed file and its companion _ERROR.txt file. 2. The _ERROR.txt file contains the full error details. 3. Fix the underlying issue (network, credentials, endpoint URL). 4. Files in the error folder are NOT automatically retried.
  • When to escalate: If the error is not related to network connectivity or credentials.

"[MOJIX-EXPORT] Failed to deserialize Mojix submission: {filePath}"

  • What it means: The export file in the queue could not be read.
  • Common causes: 1. File was corrupted. 2. File was partially written.
  • Resolution: Delete the corrupted file from the todo/ folder. The next successful validation will create a new submission.
  • When to escalate: If this happens repeatedly.

"[MOJIX-EXPORT] Error processing Mojix submission file: {filePath}"

  • What it means: An unexpected error occurred while processing a submission file.
  • Common causes: Various -- check the full error message in the log.
  • Resolution: Check the log for the full stack trace.
  • When to escalate: Always -- this indicates an unexpected error.

"[MOJIX-EXPORT] No export enabled for CargillRfid mode"

  • What it means: CargillRfid validation is running but no export service is turned on.
  • Common causes: All three export flags (EnableMojixExport, EnableMweExport, EnableAisExport) are set to false.
  • Resolution: Enable the correct export in appsettings.json and restart.

"[MOJIX-EXPORT] Cannot create submission for case {caseId}: {message}"

  • What it means: The export submission could not be created from the validation result.
  • Common causes: The validation result is missing required data (for example, no RFID data).
  • Resolution: Check the log for the specific missing data.
  • When to escalate: If this happens for results that appear to have all required data.

"[MOJIX-EXPORT] Failed to create submission file"

  • What it means: The submission JSON file could not be written to disk.
  • Common causes: 1. Disk is full. 2. Folder permissions issue. 3. Path does not exist.
  • Resolution: Check available disk space and folder permissions for C:\gatekeeper\conveyor\data\ais\todo\.
  • When to escalate: If disk space and permissions are fine.

MWE Export Errors

MWE export uses the same file-based pattern as Mojix. Error messages follow the same structure but with "MWE" in the log prefix.

"[MOJIX-EXPORT] Failed to create MWE submission file"

  • What it means: The MWE fallback file could not be written.
  • Common causes: Same as Mojix file creation errors.
  • Resolution: Check disk space and permissions.

AIS Export Errors

"Cannot create AIS submission for case {caseId}: {message}"

  • What it means: AIS export data could not be created.
  • Common causes: Validation result is missing RFID data (RFID data is required for AIS submissions).
  • Resolution: Check that the RFID reader is connected and reading tags.
  • When to escalate: If RFID is working but AIS submissions still fail.

Export Queue Locations

Folder Purpose
C:\gatekeeper\conveyor\data\ais\todo\ Pending submissions waiting to be sent
C:\gatekeeper\conveyor\data\ais\processed\YYYYMMDD\ Successfully sent submissions (archived by date)
C:\gatekeeper\conveyor\data\ais\error\YYYYMMDD\ Failed submissions that exceeded max retries

See Check Export Queue for how to inspect these folders.