I was having a similar problem with an occasional (almost once per day) failure where my bot stopped with an Error Code 0. I chased mine down by noting the time it occurred and then checking the event log on the Orchestrator server. IIS has some kind of garbage cleanup/cache flush process that was scheduled every 25 hours on the server where Orchestrator was running. During that period, Orchestrator was essentially down, and my get next transactions activities would timeout. The fix options were to either change the IIS cleanup schedule so that the down time happened on a more predictable time when my job wasn’t running, or to extend the timeout parameter for the get next transaction to like 5 or 10 minutes so that it would essentially wait for the server to come back. (Or put it in a T/C block and check for a Error Code 0 condition and then delay and try again depending on your particular needs). We ended up just extending the timeout parm.
Yoichi
Raja.G
mkt.scott4