Print shipment confirmation sometimes returns 404

[Magnus Vadla]

Hello,

For one of our customers we have experimented a bit with this report. The default shipment confirmation report has been replaced with a template that takes a purchaseReceipt number as input instead of a shipment number. This client uses dropshipment receipts instead of regular shipments.

This works well most of the time, but ~5% of GET shipmentConfirmation calls return 404 "document with number 1234 could not be found".

We have not found a pattern behind this that distinguishes the failed ones from the rest. When we pull up the report in the UI and run it with one of the failed receipt numbers there it works fine.

Best regards,

Magnus Vadla

[Magnus Vadla]

I have a theory as to what might be happening here. Do you validate that the shipment exists before generating the report?

That would explain why it works if there happens to exist a shipment with the same number as the receipt we are providing.

[Magnus Vadla]

As soon as the receipt has been released. I also experimented with a 30 seconds delay, but the issue persisted.

[Yıldırım]

I see, could you send your API Client ID & Company ID to developersupport@visma.com, so we'll check the logs in detail 

Thanks.

[Magnus Vadla]

Sorry for the delay. I just sent an email with three examples

Magnus

[Yıldırım]

Hello Magnus, 

how long after are you making printShipmentConfirmation request, after dropshipment receipts created ?