Errors are dropped in RemoteControl.SendMessageToProcess.vi (Generate User Event is gated on error in), so a failed remote command sends no reply and the REP socket stops accepting requests.
Fix: always fire the event, carry the error in the event payload, and have RemoteControl Process format the error response ({code, message, data?} + request id) via Create Response; extend Create Error Object to render app codes; clear the error in the caller so it isn't also treated as an instrument fault.
Errors are dropped in RemoteControl.SendMessageToProcess.vi (Generate User Event is gated on error in), so a failed remote command sends no reply and the REP socket stops accepting requests.
Fix: always fire the event, carry the error in the event payload, and have RemoteControl Process format the error response ({code, message, data?} + request id) via Create Response; extend Create Error Object to render app codes; clear the error in the caller so it isn't also treated as an instrument fault.