Offline messages lost?

[barsnick]

OCPP Version

OCPP2.0.1

Describe the bug

On connection issues, I observed the following issue multiple times:

2025-09-23T05:20:11.011793+0200 tarragon manager[4741]: [ERRO] ocpp:OCPP201     :: Could not send message, this is most likely because the charge point is offline.
2025-09-23T05:20:11.016336+0200 tarragon manager[4741]: [INFO] ocpp:OCPP201     :: The message in flight is transaction related and will be sent again once the connection can be established again.
2025-09-23T05:20:12.687257+0200 tarragon manager[4741]: [ERRO] ocpp:OCPP201     :: Received a CALLRESULT OR CALLERROR without a message in flight, this should not happen

It looks like it is going through the classic offline behavior:

• detect offline
• cache message
• detect online
• resend message

But it seems like it cannot correlate the lost or cached sent message with the CallResult, or wasn't expecting the latter.

Since there is a "CALLRESULT OR CALLERROR" over a second after detection of offline state, it must have gone back online. The logs don't indicate this though. Perhaps there's an internal state mismatch between assuming to be offline, and receiving messages.

Unfortunately, neither of the two calls could be traced in the OCPP message log. (Should they be there?) And I don't have a PCAP trace to see what is happening. (Will update with a trace if I manage to reproduce this.)

To Reproduce

No response

Anything else?

No response

[Pietfried]

Hi @barsnick , it would indeed be helpful to have EVerest console + OCPP logs. The message attempts should be visible in the logs and it would also help the evaluate if the CALLRESULT or CALLERROR should be handled differently.