worker-ish: compilation errors don't report the step or code in which the error occured

[josephjclark]

I'm looking at a customer's workflow. It's failing for some mysterious reason and they can't work out why.

The logs only say this:

R/T Run complete with status: crash
CompileError: 7f2d5da0-ff9b-4a2a-8942-478d7e4251bc: Unexpected token (2:14)

There are like 12 steps in this workflow.The error could be in any one of them.

We really need to report more information and probably a clearer error.

This occurs during compilation in the engine, which happens before the run actually starts. There's an issue around this because it's not ideal. There's also problems like: a syntax error in an orphaned job will still cause the whole workflow to fail.

[josephjclark]

I'm going to take a look at this fairly urgently because it's very annoying for users, and maybe not a big deal to fix?