Workflow succeeds even if a custom action fails
I saw this while I was demoing and could not capture logs etc. But the custom action failed because it ran longer than a short transaction; that transaction timed out and then the commit failed. The workflow showed as completed anyway.
I believe that this issue also leads to hydrator pipelines to show as Succeeded, even though the mapreduce for that pipeline fails, since the MR client is in a WorkflowAction.
I have observed that this is an issue in a distributed environment, but not an issue with CDAP SDK (I tried 3.3.0).
The same is true if a MapReduce fails as a part of a workflow.