# Invalid FieldReference
**URL:** https://discuss.elastic.co/t/invalid-fieldreference/324365
**Category:** Logstash
**Created:** [January 31, 2023, 7:01pm UTC](https://discuss.elastic.co/t/invalid-fieldreference/324365 "2023-01-31T19:01:58Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@ztony](https://discuss.elastic.co/u/ztony)
#### Post date: [January 31, 2023, 7:01pm UTC](https://discuss.elastic.co/t/invalid-fieldreference/324365/1 "2023-01-31T19:01:58Z")
Does anyone see this "Invalid FieldReference" error? we added some mutations to the pipeline, but new field with the same error came out. see the error log below:
An unexpected error occurred! {:error=\>org.logstash.FieldReference$IllegalSyntaxException: Invalid FieldReference: `_ldapEntity_SkippedAddresses[0]`, :backtrace=\>["org.logstash.FieldReference$StrictTokenizer.tokenize(FieldReference.java:315)",
---
### Author:  [@Badger](https://discuss.elastic.co/u/Badger)
#### Post date: [February 1, 2023, 2:51am UTC](https://discuss.elastic.co/t/invalid-fieldreference/324365/2 "2023-02-01T02:51:30Z")
What did you change in the pipeline immediately before the errors started occurring?
---
### Author:  [@ztony](https://discuss.elastic.co/u/ztony)
#### Post date: [February 5, 2023, 3:14pm UTC](https://discuss.elastic.co/t/invalid-fieldreference/324365/3 "2023-02-05T15:14:19Z")
Hi Badger, thank you for your reply. We applied a patch, this issue has been resolved. this thread can be closed. thank you!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 5, 2023, 3:14pm UTC](https://discuss.elastic.co/t/invalid-fieldreference/324365/4 "2023-03-05T15:14:32Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.