Error cases

Errors can occur on both system while processing messages via VDV 463. In case of any errors the corresponding system must send error messages instead of confirmation messages.

Example error message sent by ChargePilot®

The error message payload sent by ChargePilot® will always have the following structure, containing a property message with error explanations.

[
    3,
    "CMS",
    "Presystem1",
    "2023-09-13T10:04:14.645Z",
    "baf4ad01-d220-4430-a3eb-b31e4999720e",
    "ProvideChargingRequests",
    {
        "message": "Charging requests for ids: 692bc7f3-93b6-47f6-8efd-d5550aa393e5, 97048f7b-ed64-4cf4-9b9d-94120c5bdc47 does not exist."
    }
]

Example error message sent by Upstream System

In case of error message sent by the Upstream System, there is no fixed agreement upon the error explanation property. The rest of the error message should be structured as shown below.

[
    3,
    "BMS",
    "Presystem1",
    "2023-09-13T10:04:14.645Z",
    "baf4ad01-d220-4430-a3eb-b31e4999720e",
    "ProvideChargingRequests",
    **Any value**
]