RDP 3.82 "Other return codes" bug

[Rich Dowling]

We've found that if you set an "Other return code" on a job step with settings "Stop" and "Success" then it fails to stop and continues to the next step.

If you set it to "Stop" and "Failure" it does stop, but obviously you get a red "x" for the job status.

If you delve into the status detail with it set to stop and success, the message is:
"The I/O operation has been aborted because of either a thread exit or an application request."

If it's set to stop and failure, the message is shown correctly as the text entered for this specific return code.