Pipeline errors are not obvious and not necessarily informative

[ebranlard]

Example: apply a mask which returns no data. An informative Exception is triggered, but the Action will convert that to a non informative Exception.

It's not obvious to the user that an error as occurred unless they look at "Errors(1)" in the pipeline.

Solution:

• Keep the informative Exception
• Pop up error at the end of pipeline.

Issue raised by @mayankchetan

[ebranlard]

Fixed in 0f6efd729bba220471d379a2e8b03d8121718316