Orchestrators that simply throw an exception have that exception "swallowed"

[davidmrdavid]

Consider an orchestrator that simply runs:

throw "oops!"

The orchestrator will correctly be labeled as Failed, but the error message will read "With OOProc schema V3, expected actions array to be of length 1 in outer layer but got size: 0""

The correct behaviour is that the error should be that of the exception in the user code.

[davidmrdavid]

FYI @hossam-nasr

[davidmrdavid]

Relatedly: it seems that throw statements that do not throw an Error type are not correctly propagated either. In other words, the only exceptions that are correctly propagated are those that throw an Exception-type.

For instance: throw new Error("oops!"); will work, but throw "oops!" will not.