Debugging and error handling

Order related issues

You can tackle many order-related errors by adding an error_email_address to the order payload. When something goes wrong, we'll (automatically)email you valuable debug information. Make sure you have access to the mailbox you supply in the error_email_address

Error mail address

The property error_mail_address is an array of strings and is supplied at the root level of the order object.

Example for the order payload

{
  ...
  "error_email_addresses": [
    "${order.error.email}"
  ],
  ...
}

Issue: Delivery date bounced

In some cases, the delivery date/shipping method combination is no longer valid. This can be due to the cutoff times. *

*How to resolve * Try sending the order again. If the issue remains, please validate the configuration on your Probo Platform or perform a /price call

Issue: Can not find unique id for option

The product configuration in the order payload is not valid; this can be due to a missing option or the product configuration has changed.

*How to resolve * Try sending the order again. If the issue remains, please validate the configuration on your Probo Platform or perform a /configuration call

Price-related issues

The price-related calls can often be related to some misconfiguration

Issue: code: 500 when using API products (customer_code)

This issue is due to an invalid API Product code. Please check if this configuration is still valid