Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
Pipes 2.0.2
-
None
Description
While not breaking the pipe execution at the first issue encountered is important in a production world when a content exception should/could be handled separately. Errors happening are "only" happening on logs.
They should be tracked in the execution result as well, with path excerpt, and total #, with same limit as for results.