> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/troubleshooting-and-resources/armory/general/errors-dont-propagate-from-child-to-parent-pipelines.md).

# Errors don't propagate from child to parent pipelines if they occur in stages configured to "ignore

### Issue <a href="#issue" id="issue"></a>

Error messages don't propagate from child to parent pipelines if they occur in stages configured to `ignore the failure`. In these instances, the parent pipeline will not have enough information to appropriately handle the child pipeline's error.

### Cause <a href="#cause" id="cause"></a>

This happens when a stage in the child pipeline has been set to `ignore the failure` if the stage fails (under `Execution Options`). If an error occurs in this stage, Spinnaker still considers the pipeline successful because the failure was ignored due to the setting, and even though the stage execution will display an error, the pipeline execution is not considered as "having failed" and will not signal as such. *note* Certain types of error will cause the entire pipeline to fail, even if the stage is set to `ignore the failure`. In the case of these "grand failures," Parent pipelines may fail.