GetTransactionStatus
Asks whether a transaction is still running and whether the station has events it has not delivered.
- Version
- OCPP 2.0.1
- Direction
- CSMS → Charge Point
- Functional block
- Transactions
New in 2.0.1, and there is no 1.6 equivalent. It answers the question a CSMS has after any reconnection: does this station still have transaction data I have not seen?
Omitting transactionId asks about the station as a whole — useful before a reset.
Request
| Field | Type | Required | Description |
|---|---|---|---|
transactionId | string | Optional | The transaction to ask about. Omit to ask about all of them. |
json
[2, "19223201", "GetTransactionStatus", {
"transactionId": "a1b2c3d4-0001"
}]Response
| Field | Type | Required | Description |
|---|---|---|---|
messagesInQueue | boolean | Required | True when the station is still holding undelivered transaction messages. |
ongoingIndicator | boolean | Optional | True when the transaction is still running. |
json
[3, "19223201", {
"ongoingIndicator": true,
"messagesInQueue": false
}]Implementation notes
Call this before an `Immediate` reset. messagesInQueue: true means a restart will lose billing data that has not reached you yet.
It is also the correct way to reconcile after a CSMS outage, instead of inferring open sessions from the last event you happened to receive.