system.opcua.callMethod: BadInvalidState

Hi, I am making heavy use of the system.opcua.callMethod function. An example of a typical call is:
image
but serialnumber_details_CQ is by far not the only opcua method I call on the OpcRouter server.
My calls happen asynchronously: some calls are originated by a gateway timer, some more by mobile devices handled by operators in the factory, so that it is not defined if calls can overlap or start just at the same time. Most of the time each call works correctly, but sometimes I log a bad result:
Screenshot from 2024-10-16 14-56-36
and the operator does not get the expected answer.
When that error occurs, if I read through the OPC UA server log, I find no log of an incoming OPC UA method call. Therefore I think that in those cases my call stops at the Ignition gateway.
Any idea about possible reasons? Workarounds?

Thanks in advance, regards

This StatusCode comes from the server, so the call must be happening. I’m afraid you need to look at the server for answers. Wireshark would capture the call as it’s being made and responded to. Not sure if that will help.

Many thanks @Kevin.Herron , I will investigate further