> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/live-content-cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/live-content-cloud/support/faq.md). # Common issues ## What does \[Strict field resolution and no field mapping...] error mean? A common error when creating a stream is the following: ``` Strict field resolution and no field mapping can be found for the field with name [XXX] ``` The error is returned if the supplied query includes a field (in this case named `XXX`) that does not exist in the ElasticSearch index where the query is to be stored. So, why does it not exist in the database? Well, that is because the fields in the ElasticSearch index is created on the fly when they first appear in property in a document notified by OC. The reason for the error is one of the following: * The spelling of the field in the query is wrong. It does not match the property name configured in OC.\ \&#xNAN;*Solution:* Fix the spelling * QS has never received a document from the OC Notifier that includes the property.\ The reason is one of the following: * The notifier is broken. Either its not runing correctly or the notification rule for QS is not present or invalid.\ \&#xNAN;*Solution:* Check that the notifier is started, runs and has a correctly configured notification rule of QS. * No document has ever been created in OC with a value in that specific property.\ \&#xNAN;*Solution*: Create (or update) a document so that the missing property is populated. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.navigaglobal.com/live-content-cloud/support/faq.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.