Closed HenKun closed 3 years ago
Hi @HenKun
that is a tricky situation here. Most likely, the label creation succeeded in the DHL systems but the (positive) response was not received in time.
Based on such an empty response, we cannot make assumptions about the "actual" progress of shipment order processing in the remote systems. From the module perspective, anything but a positive response indicates a failure.
When the shipping label is created manually through the packaging popup, then no error comments are added because the admin user receives immediate feedback in the UI. When the shipping label is created automatically (cron or bulk), then a generic error is added to the order/shipment comments in such cases:
Label could not be created: Web service request failed.
Maybe this is sufficient to watch out for possibly affected shipment orders – if it is worth the effort.
Hello @mam08ixo ,
yes, I see the issue. Maybe it would be a little improvement if in such cases the error messages are more specific, so that the non-technical packing worker knows what could have happened:
1) On bulk or cron processes: Comment to the shipment: "Web service request failed. A label might have been created, please go to DHL Business Portal. "
2) On manual processes: UI Message: "Web service request failed. A label might have been created, please go to DHL Business Portal. ", Additionally a note/comment to the shipment would also be of benefit for future reference.
@HenKun That does actually make sense. I've looked through some older support cases and found (after some digging) that this can indeed happen. We're going to change the error message and documentation accordingly.
Internal ref: DHLGW-1049
Error message and documentation were updated with the 1.5.1 release.
We faced an issue, where the DHL Soap Server did not responded correctly or in time (I guess so), when a label was requested.
The error was logged, however, not visible in backend, which led to confusion:
What happened:
dhlpaket.ERROR: Error Fetching http headers
Images of Magento Backend
Log of the first failed attempt
Log of the second attempt
Proposed solution