COM run jobs and queues

My 2 cents... when you run it in detached mode, the job is unable to find the other job you want to send to a queue and that's why you get an error occurring "…while executing runjobs. Error: Null object reference"
That Null object reference error in turn leads to the crash. A detached job cannot access other jobs.

When you run it in the interactive debugger or run it in Test mode, you run it in the foreground as a non-detached job and it works ok.

Yes, thats definitely what I'm seeing but for reference RunJob Jal method works fine on a detached job just not JobSendToQueue.

This is fine as a limitation it does make sense but at the same time it's not documented and the failure is not handled cleanly or reported usefully.

I agree with you on both points. All errors should be handled gracefully and correctly reported