# \[Ingest Node\] pipeline with id \[x\] does not exist (solved)

**URL:** <https://discuss.elastic.co/t/ingest-node-pipeline-with-id-x-does-not-exist-solved/54436>\
**Category:** Elasticsearch\
**Created:** [June 30, 2016, 3:55pm UTC](https://discuss.elastic.co/t/ingest-node-pipeline-with-id-x-does-not-exist-solved/54436 "2016-06-30T15:55:08Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![PatrickKik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrickkik/32/619_2.png) [@PatrickKik](https://discuss.elastic.co/u/PatrickKik)\
**Post date:** [June 30, 2016, 3:55pm UTC](https://discuss.elastic.co/t/ingest-node-pipeline-with-id-x-does-not-exist-solved/54436/1 "2016-06-30T15:55:08Z")

</div>

SOLVED  
Just minutes before the release of `5.0.0-alpha4` I found this bug.  
I tried it in `5.0.0-alpha4' and it works fine. That's nice. But it still feels like I have lost some time... 😩

I'm using `elasticsearch-5.0.0-alpha3` and `kibana-5.0.0-alpha3`.

Using Console I register a pipeline:

```
PUT _ingest/pipeline/x
{
  "description": "Ingesting Meetup events",
  "processors": [...]
}

```

When I check if my pipeline exists:

```
GET _ingest/pipeline/x

```

It comes back the way it should:

```
{
  "pipelines": [
    {
      "id": "x",
      "config": {
        "description": "x",
        "processors": [...]
      }
    }
  ]
}

```

But when I want to use it:

```
PUT a/b/c?pipeline=x
{
  "z": 0
}

```

The response is:

```
{
  "error": {
    "root_cause": [
      {
        "type": "illegal_argument_exception",
        "reason": "pipeline with id [x] does not exist"
      }
    ],
    "type": "illegal_argument_exception",
    "reason": "pipeline with id [x] does not exist"
  },
  "status": 400
}

```

Also tried using `curl` but I've got the same result.

Is there something I'm missing? Or is this a bug?

---

_[View the full topic](https://discuss.elastic.co/t/ingest-node-pipeline-with-id-x-does-not-exist-solved/54436)._