- a JobFlow execution is terminated as soon as any graph or JobFlow component encounters an exception/error, and
- the origin of the exception/error is clearly visible at the JobFlow level sp my server's administrator doesn't have to dig to find them
For example, if my JobFlow's third Graph executes a DB sproc which raises an error with a message, I'd like my Clover server admin to see that error message in the Execution History --> Overview --> Error Message field. Is there a usual pattern for such requirements?
Thank you for any insights,