# Ingest pipeline processors what constitutes a failure?

**URL:** <https://discuss.elastic.co/t/ingest-pipeline-processors-what-constitutes-a-failure/277980>\
**Category:** Elasticsearch\
**Created:** [July 6, 2021, 3:30pm UTC](https://discuss.elastic.co/t/ingest-pipeline-processors-what-constitutes-a-failure/277980 "2021-07-06T15:30:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sam3546](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sam3546/32/79281_2.png) [@sam3546](https://discuss.elastic.co/u/sam3546)\
**Post date:** [July 6, 2021, 3:30pm UTC](https://discuss.elastic.co/t/ingest-pipeline-processors-what-constitutes-a-failure/277980/1 "2021-07-06T15:30:50Z")

</div>

If i use an ingest pipeline with a processor of some kind say an enrich processor and i provide a valid enrich policy with valid fields to match and enrich. If no match is found i assume this would not constitute a failure? It would ignore and move on to the next part of the pipeline?

Is there a format that would give me essentially an onNoMatchFound(do x (set field 'match\_found' to false)) (i know this isn't a property of the enrich processor but im looking for a pipeline setup that would act in that way)

Or am i not understanding onFailure() correctly?

Apologies if that does not make much sense.

Cheers

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 3, 2021, 3:31pm UTC](https://discuss.elastic.co/t/ingest-pipeline-processors-what-constitutes-a-failure/277980/2 "2021-08-03T15:31:12Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.