# Functionbeat does not update documents with existing \_id **URL:** \ **Category:** Beats\ **Tags:** functionbeat\ **Created:** [October 21, 2020, 9:16pm UTC](https://discuss.elastic.co/t/functionbeat-does-not-update-documents-with-existing-id/252901 "2020-10-21T21:16:05Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![amiPorat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/amiporat/32/77642_2.png) [@amiPorat](https://discuss.elastic.co/u/amiPorat)\ **Post date:** [October 21, 2020, 9:16pm UTC](https://discuss.elastic.co/t/functionbeat-does-not-update-documents-with-existing-id/252901/1 "2020-10-21T21:16:05Z")
Hello, I am currently deploying Functionbeat configured to accept events from an SQS queue. The goal is to use a processor/ingest pipeline to extract and set \_id from fields in the incoming messages. Documents with existing \_id do not appear to be pushed from functionbeat at all. I have attempted to isolate the behavior with the below steps: - Write message to aws sqs queue i.e. aws sqs send-message --queue-url \ --message-body '{ "val": "foo", }' --message-group-id f1 --message-deduplication-id 1 Doc is successfully written to ES, with \_id: \. - Take the ID from the created message above, and write the message to queue again with updated values and pass in the \_id. aws sqs send-message --queue-url \ --message-body '{ "val": "bar", "\_id": \ }' --message-group-id f1 --message-deduplication-id 2 When I do this I do not see the document being updated or rewritten at all. Any guidance here would be greatly appreciated. Thank you for your time and help. Best, Ami ---
**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\ **Post date:** [October 21, 2020, 10:45pm UTC](https://discuss.elastic.co/t/functionbeat-does-not-update-documents-with-existing-id/252901/2 "2020-10-21T22:45:41Z")
Do you see the second document (the one with the `_id` set being indexed as an _entirely new_ document in Elasticsearch? ---
**Author:** ![amiPorat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/amiporat/32/77642_2.png) [@amiPorat](https://discuss.elastic.co/u/amiPorat)\ **Post date:** [October 21, 2020, 11:46pm UTC](https://discuss.elastic.co/t/functionbeat-does-not-update-documents-with-existing-id/252901/3 "2020-10-21T23:46:11Z")
The second document does not show up at all. ---
**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\ **Post date:** [October 26, 2020, 8:24am UTC](https://discuss.elastic.co/t/functionbeat-does-not-update-documents-with-existing-id/252901/4 "2020-10-26T08:24:35Z")
Hmmm, @kvch any idea why this might be happening? I would've expected the second document to show up as an entirely new document in ES (essentially ignoring the `_id` field from the message consumed from the queue). ---
**Author:** ![tzaitsev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tzaitsev/32/78802_2.png) [@tzaitsev](https://discuss.elastic.co/u/tzaitsev)\ **Post date:** [November 11, 2020, 4:52am UTC](https://discuss.elastic.co/t/functionbeat-does-not-update-documents-with-existing-id/252901/5 "2020-11-11T04:52:44Z")
Hi all, any update here? It's been 20 days since we've escalated this and it seems like there is no activity? Is the recommendation here not to use functionbeat? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 9, 2020, 6:52am UTC](https://discuss.elastic.co/t/functionbeat-does-not-update-documents-with-existing-id/252901/6 "2020-12-09T06:52:45Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.