Closed SaMnCo closed 6 years ago
Hi @SaMnCo, sorry for the late response; I just got back from vacation.
Good catch! There is a overall timeout set for an workflow execution. So the execution would eventually stop after 10 or so minutes. But of course an error like this should stop the workflow earlier than that. Not sure if we even want to retry at all on an expression error.
Aside, we are working on removing the manual YAML->JSON step. :)
Fixed in #60 - workflows no longer require the manual compilation to JSON.
"2017-10-20T08:47:26Z" level=error msg="Failed to parse input: TypeError: Cannot access member 'risk' of undefined" inputKey=if val=type:"expr" value:"{$.Tasks.SetToPending.Output.risk > 70}"
As I understand it, this issue is not about compilation to JSON, but about errors in JSON expressions in input fields of tasks.
My bad! My checking on open issues, I misread that this issue was regarding the yaml conversion. Thanks @soamvasani !
Errors in json now fail the task immediately.
I have a very simple workflow like:
the inputs are supposed to be JSON. I made a mistake calling the function and my JSON was malformed. Then the workflow engine goes crazy and retries for ever:
I could not find a way to stop that. Currently the only option I found is to do
Is there another and better way?
Thanks!