Why is my batch in error?

A batch goes into error when a consistency point blocks its processing.

Purpose of the article

Identify the most likely cause of a batch error, check the blocking elements and know what to do next.

Observation

The error may come from missing information, an inconsistent status, poor attachment or data that is not compatible with the batch.

Possible causes

• Status of non-compliant batch: the batch is not in the expected state to continue processing.
• Incomplete information: Mandatory data is missing on a mission or lot.
• Bad connection: The mission, partner or tracking item is not correctly associated.
• Business inconsistency: an overlap, missing validation, or data incompatibility blocks the batch.

Checks to be made

1. Read the displayed message: note the exact text of the error.
2. Check the status: check if the batch or DTR is in the correct condition.
3. Check key data: mission, partner, driver, vehicle or invoice as applicable.
4. Locate the blocking element: identify the point that prevents further treatment.

What to do next?

• Correct the data if the error is identifiable.
• Relaunch only after complete correction.
• If the blockage remains unexplained, prepare a support ticket with the useful elements.

Information to send to support

• Batch reference.
• Mission or DTR reference.
• Partner concerned.
• Date and time of report.
• Capture with full error message.

In summary

• An error batch must be analyzed based on the message displayed and the processing status.
• First check the data and attachment before escalating.

Need help?

If no checks can identify the cause, contact support via support@waynium.com with the diagnostic elements.