# Elasticsearch Engineer Training - Lab 4.2/4.3 - 404 during update by query

**URL:** <https://discuss.elastic.co/t/elasticsearch-engineer-training-lab-4-2-4-3-404-during-update-by-query/284677>\
**Category:** Elastic Training\
**Created:** [September 21, 2021, 5:41am UTC](https://discuss.elastic.co/t/elasticsearch-engineer-training-lab-4-2-4-3-404-during-update-by-query/284677 "2021-09-21T05:41:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![efd6](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/efd6/32/94818_2.png) [@efd6](https://discuss.elastic.co/u/efd6)\
**Post date:** [September 21, 2021, 5:41am UTC](https://discuss.elastic.co/t/elasticsearch-engineer-training-lab-4-2-4-3-404-during-update-by-query/284677/1 "2021-09-21T05:41:08Z")

</div>

I have a problem with the elasticsearch training in module 4.2 and 4.3 (only 4.3 included since it's shorter and the problems are the same).

When I create a policy and execute the policy index creation and then construct the transform pipeline, I get success, but when I attempt to update by query, I get a failure with 404.

```auto
PUT _enrich/policy/webtraffic_policy
{
  "match": {
    "indices": "traffic_stats",
    "match_field": "url.original",
    "enrich_fields": ["@timestamp.value_count", "runtime_ms.avg"]
  }
}

POST _enrich/policy/webtraffic_policy/_execute

PUT _ingest/pipeline/webtraffic_transform_pipeline
{
  "processors": [
    {
      "enrich": {
        "field": "url",
        "policy_name": "webtraffic_policy",
        "target_field": "traffic_stats"
      }
    }
  ]
}

POST blogs_fixed3/_update_by_query?pipeline=webtraffic_transform_pipeline?wait_for_completion=false

```

Here is the head of the errored response. It looks to me like `wait_for_completion=false` parameter is being included in the pipeline ID.

```auto
{
  "took" : 181,
  "timed_out" : false,
  "total" : 4659,
  "updated" : 0,
  "deleted" : 0,
  "batches" : 1,
  "version_conflicts" : 0,
  "noops" : 0,
  "retries" : {
    "bulk" : 0,
    "search" : 0
  },
  "throttled_millis" : 0,
  "requests_per_second" : -1.0,
  "throttled_until_millis" : 0,
  "failures" : [
    {
      "index" : "blogs_fixed3",
      "type" : "_doc",
      "id" : "qRKJAHwBQJh2eNuxyEoi",
      "cause" : {
        "type" : "illegal_argument_exception",
        "reason" : "pipeline with id [webtraffic_transform_pipeline?wait_for_completion=false] does not exist"
      },
      "status" : 400
    },
...

```

Can someone tell me what I'm not understanding here?

thanks

---

<div class="post-metadata">

**Author:** ![efd6](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/efd6/32/94818_2.png) [@efd6](https://discuss.elastic.co/u/efd6)\
**Post date:** [September 21, 2021, 6:53am UTC](https://discuss.elastic.co/t/elasticsearch-engineer-training-lab-4-2-4-3-404-during-update-by-query/284677/2 "2021-09-21T06:53:37Z")

</div>

Solved: The text provided by the instructions for 4.2 step 12 is incorrect and I missed the typo; the second `?` should be `&`. I then reused and modified the incorrect text in the second instance at 4.3 step 9 where the provided text is correct.

---

<div class="post-metadata">

**Author:** ![dinyes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dinyes/32/42906_2.png) [@dinyes](https://discuss.elastic.co/u/dinyes)\
**Post date:** [September 21, 2021, 1:38pm UTC](https://discuss.elastic.co/t/elasticsearch-engineer-training-lab-4-2-4-3-404-during-update-by-query/284677/3 "2021-09-21T13:38:13Z")

</div>

Good catch! I've got a ticket open to get this fixed.

---

<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:** [October 21, 2021, 1:38pm UTC](https://discuss.elastic.co/t/elasticsearch-engineer-training-lab-4-2-4-3-404-during-update-by-query/284677/4 "2021-10-21T13:38:58Z")

</div>

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