Troubleshooting exit code 141

Our server console app exited today with code 141 (SIGPIPE, or “broken pipe”, I think). Since we have all code wrapped in Try/Catch blocks and have implemented App.UnhandledException (which doesn’t seem to get called), I wonder what the best way to track this might be? We can’t reproduce it, of course, and this server often keeps running for days without issue. (We update at least weekly so it never gets a chance to go longer than that.)

AFAIK signals aren’t catachable in Xojo - at least not “safely”
They’re like interrupts in many ways

And certainly not with try catch

About the best you can do is have a mechanism to restart your server app ASAP