actions in a looped flow are cancelled without obvious reason

Document ID : KB000007002
Last Modified Date : 14/02/2018
Show Technical Document Details

action is cancelled due to ancestor's failure yet the ancestor completed well.

Release Automation 5.5 and higher

The error is misleading. It says "Cancelled due to ancestor's failure" but this error also occurs when a loop that starts right after the ancestor has 0 iterations, i.e. the actions within it do not run at all.


Find out why the collection elelement or xml file that the looped flow is based on is empty. Then correct it so the flow is executed at least once.

Additional Information:

A common cause of an empty artifact related collection element is that the artifact definition is not mapped to the same server type as the process that runs the flow.