While building a workflow I noticed the following issue:
If an error happens inside a function, the run will still go through without stopping. Inside the logs the errors also appear but nowhere else. Which means you have to manually check the workflow manually every time it runs. Which is highly suboptimal for the workflow I'm building that's supposed to run every day. It also doesn't start the global error handler sadly. Below is a Screenshot where you can see the issue in an example workflow I created.
I am facing the same problem. This is really a big issue, errors go unnoticed like this and then global error handler becomes useless as it is unreliable. It makes no sense since the error is there in the log, but no error or failure is being triggered.
I'll bump this too - at the very least is there a way to push any function error information as objects into an array that could be added to the workflow response?
The name of the function is UpsertCategoryChildren and the name of the parameter is the same. Within the function, you seem to be trying to call your function recursively, but because the name of the parameter is also UpsertCategoryChildren, and the argument passed in line one is '333', we are basically trying to invoke this function: '333'('333').
Could you expand on what is that we are trying to achieve with this function? I'm happy to help.
