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.

Release Notes



Ali Anwar
February 4, 2016, 2:43 AM

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.

Ali Anwar
January 26, 2016, 9:37 PM

I have observed that this is an issue in a distributed environment, but not an issue with CDAP SDK (I tried 3.3.0).

Ali Anwar
January 19, 2016, 8:35 AM

The same is true if a MapReduce fails as a part of a workflow.



Sagar Kapare


Andreas Neumann