> 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.7.md). # 6.4.7 ## Features * **Improved InputQueue circuit breaker resilience** — The input-queue circuit breaker now stores all of its polling state directly in Redis as the single source of truth, so new or restarted pods automatically pick up the shared state with no manual sync or startup restore. The `INPUT_QUEUE_STATUS` job now runs on both worker and API nodes (a distributed lock ensures only one run per cycle), and the circuit breaker state (state, message count, bytes, reason) is now exposed via the `/system/health` API. ## Bug Fixes * **Fixed RabbitMQ consumer ack-timeout that could stall input-queue consumption** — When many slow-running messages are being processed, messages prefetched from RabbitMQ could sit un-acked in the in-memory Throttle queue long enough to trip RabbitMQ's `consumer_timeout`, causing it to close the channel and halt consumption from the input queue until reconnect. A message that waits in the Throttle queue longer than `THROTTLE_QUEUE_TIMEOUT` (default 5 minutes) is now re-published as a fresh copy and the original is acked, returning it to the broker before the channel can time out — with no message loss. A longer backstop guard (`BROKER_MESSAGE_ACK_TIMEOUT`, default 28 minutes) frees the channel as a last resort if a message is still unacked after processing begins. --- # 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.appmixer.com/changelog/version-6/6/6.4/6.4.7.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.