> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/changelog/version-6/6/6.4/6.4.11.md). # 6.4.11 2026-08-28 ## Bug Fixes * **Fixed log records being dropped by Elasticsearch when they carried an `_id` field** — Log extras are flattened into the top level of the log record, and Elasticsearch reserves leading-underscore keys there for its own metadata, so any log call passing `_id` had its whole document rejected with a 400 and never indexed. The MinIO GridFS migrator was doing exactly that in its `Skipping file with missing metadata` warning (which fires on every plugin start for interrupted uploads), so those warnings were lost. The field has been renamed, and log record creation now moves any reserved key under a prefixed name (`_id` → `extra_id`) instead of letting the record be dropped — this also protects log calls in customer-written system plugins. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.appmixer.com/changelog/version-6/6/6.4/6.4.11.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.