Hey Paul, thanks a lot for you answer.
We don’t use Should Stop yet, although we are aware of it and planning to study it for future bots.
In this specific case, however, I got the following error:
RemoteException wrapping System.Exception: Job stopped with an unexpected exit code: 0x40010004
The error was logged about 15 minutes after the job started, but the job was “Stopping” for more than 24 hours and only then it stopped. As all of this happened during the weekend, we only became aware of it this morning.
This error seem to have something to do with the VM. Our IT team is taking a look at it.
Anyway, I don’t know how to bypass this kind of thing on the bot code. I would appreciate any tip regarding that.
That’s why I asked if there was a way to send a Kill command (not a Stop one) when making an API call to Orchestrator. A Kill command with 20 minutes limit would be perfect for this particular case.