Use the original error(s) within the ‘Halt’ action or something similar

1

Dear @dgudkov
I am using this pattern frequently, and I think this really works well.
But if your flow is executed as a task within the server, the error is not logged within the task journal. I know you can use the ‘Halt’ action and set an error message, but you can not use parameters for this. So is it possible to use the original error(s) within the ‘Halt’ action or something similar. What I like to achieve is something like the .NET exceptions, where you can raise a new exception and add an existing exception as the inner exception.
Kr
Edward

2

Hi Edward,

I can suggest using the “Status” action to record errors when they appear. Then use one “Halt” action with a message, for instance: “One or more errors occurred. See the status log.”

Status messages are written in the task journal. Up to 20 messages are written.

Would that work for you?

Alternatively, we can add something like a “Halt with a list of errors” action, which would simply generate up to 20 errors with messages from an input column.

1 Like
3

This was EXACTLY what I needed :smiley:

Thank you very much!

4

You’re welcome :slight_smile: