Decision Tree: Exports Failing¶

Use this when validated data is not reaching Mojix, MWE, or AIS, or when the export queue is growing.

Step 1: Is an export service enabled?¶

Check appsettings.json for these settings:

Setting	Value
`EnableMojixExport`	`true` or `false`
`EnableMweExport`	`true` or `false`
`EnableAisExport`	`true` or `false`

At least one export must be set to true for data to be sent.

CargillRfid export priority: The system uses the first enabled service in this order: Mojix, then MWE, then AIS.

YES (at least one export is enabled) -- Go to Step 2
NO (all exports are false or missing) -- Enable the correct export in appsettings.json and restart the application.

Step 2: Is the endpoint URL configured?¶

Check the corresponding URL setting:

Export	URL Setting
Mojix	`MojixEndpointUrl`
MWE	`MweEndpointUrl`
AIS	`AisEndpointUrl`

The URL must be a complete address (for example, https://example.mojixretail.io/api/v1/events).

YES (URL is present and looks correct) -- Go to Step 3
NO (URL is empty or missing) -- Add the correct URL and restart the application. Contact the integration partner for the correct endpoint URL.

Step 3: Can the machine reach the export endpoint?¶

Open a command prompt and test connectivity:

ping <endpoint-hostname>

For example: ping chipotle.mojixretail.io

YES (ping replies received) -- Go to Step 4
NO (Request timed out or host not found) -- The machine cannot reach the export server. Check:
Network cable connection
Firewall rules (outbound HTTPS on port 443)
VPN connection (if the export endpoint requires VPN)
DNS resolution (can the hostname be resolved?)

See Check Network Connectivity.

Step 4: Are there files in the export queue?¶

Check the export queue folder:

C:\gatekeeper\conveyor\data\ais\todo\

See Check Export Queue for details.

YES (files are present in todo/) -- Go to Step 5
NO (folder is empty) -- Exports may not be generating. Check that validation is running and cases are passing. Only passed validations generate export submissions.

Step 5: Check the log for export errors¶

Open the log file and search for "MOJIX-EXPORT", "MWE", or "AIS".

Common error patterns:

Log Message	Meaning	Go To
`"Mojix submission {file} failed - retry count: X/Y"`	Export attempt failed, will retry	Step 6
`"Mojix submission {file} exceeded maximum retries"`	All retries exhausted, file moved to error folder	Step 6
`"Failed to deserialize Mojix submission"`	The export file is corrupted	Step 7
`"No export enabled for CargillRfid mode"`	No export service is turned on	Go back to Step 1
`"Cannot create submission for case {id}"`	Export data could not be created	Step 7

HTTP error codes visible -- Go to Step 6
Deserialization or creation errors -- Go to Step 7
No export log messages at all -- Go back to Step 1 to verify exports are enabled

Step 6: HTTP errors during export¶

The export service is trying to send data but the remote server is returning errors.

HTTP Status	Meaning	Resolution
401	Unauthorized	Check export credentials in appsettings.json
403	Forbidden	The machine's IP may not be whitelisted on the export server
404	Not Found	The endpoint URL path is wrong -- verify with the integration partner
500	Server Error	The remote server has a problem -- contact the integration partner
503	Service Unavailable	The remote server is down -- wait and retry, or contact the integration partner
Connection refused	Cannot connect	Network issue -- go back to Step 3
Timeout	No response	Network issue or server slow -- check firewall and contact the integration partner

Resolution: Fix the identified issue. Files in the todo/ queue will be retried automatically. Files that have exceeded the maximum retries are moved to the error/ folder with a companion _ERROR.txt file containing details.

Step 7: Export data errors¶

The export submission file could not be created or read.

Check the log for the full error message.
This may indicate a bug in the export mapping code.
Verify that validation results contain all required data (RFID EPC, barcodes, production data).

Resolution: See When to Escalate. This likely requires development team involvement.

Still not resolved?¶

If exports are still failing after following these steps, see When to Escalate and collect diagnostics using the Collecting Diagnostics guide.