HACH - Delivery Not Received in HACH Packing Module

Introduction:

This article outlines the steps to troubleshoot situations where a delivery is not being received or reflected in the HACH Packing Module. Follow the instructions below to investigate and resolve the issue.

Symptoms:

• A delivery that was expected in the HACH Packing Module is not visible.

Troubleshooting Steps:

1. Verify the Delivery Number:

   • Carefully check the delivery number that was received in the Packing Module.
   • Perform a cross-referencing activity to ensure the delivery number is correct and matches the expected delivery.

2. Check for Payload Transmission from TCS:

   • Confirm if the TCS (Transportation Corporation of India) team has sent the necessary data payload for this delivery to the HACH Packing Module.
   • If the payload has not been sent, request the TCS team to send it.

3. Manually Push the Payload (If Necessary):

   • If the payload from TCS is received but the delivery is still not in the HACH Packing Module, you may need to manually push the payload using the Postman tool.
   • Method: Use the POST method.
   • Endpoint: https://hach-pack.pando.in/api/v1/delivery/
   • Authentication: No authentication is required.
   • Payload: The payload should be in JSON format. The structure of the JSON payload will depend on the delivery details. At a minimum, it will likely contain information such as the delivery ID and associated item details. (Note: The example provided in the original content was an empty JSON object {}. You will need to replace this with the actual delivery data in JSON format.)
   • Execute the POST request in Postman.
   • Success: If the push is successful, update the Freshdesk ticket with this information and close it.

Handling the "Duplicate Delivery DetailIDs Found" Error:

If you encounter the following error message after pushing the payload:

[
  {
    "delivery_id": XXXXXXXX,
    "error": "duplicate delivery detailIDs are founded",
    "statusCode": 400
  }
]

This indicates that the system has already processed a delivery with the same deliverydetailID. Follow these steps:

1. Investigate in Loggly: Attempt to locate the previous mapping of this deliverydetailID using Loggly (or your relevant logging tool).

2. Seek Assistance from the Packing Team: If you are unable to find the previous mapping in Loggly, reach out to the PACKING Team on their designated Slack channel for assistance.

3. Update the Ticket: Once you have confirmation from the Packing Team (or find evidence in Loggly), update the Freshdesk ticket with the following information: "Reported delivery number [insert delivery number] was previously mapped and pushed to Pando for the shared DeliverydetailID."

Important Considerations:

• Ensure you have the correct JSON payload from TCS before attempting to manually push it. An incorrect payload will result in errors.
• Exercise caution when manually pushing payloads. Verify the data thoroughly to avoid creating duplicate entries or inconsistencies.
• The availability and usage of Loggly may vary depending on your organization's setup.
• Always document the steps taken and the outcome in the Freshdesk ticket for future reference.