> 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.6.md).

# 6.4.6

2026-06-16

## Features

* **Performance optimizations for the variables, auth, and coordinator APIs** — A range of optimizations to component loading and execution:
  * Constructor module loading now avoids excessive filesystem `exists` checks and eliminates redundant `require.resolve()` calls, with improved `findModulePath`/require-cache handling.
  * The Loader now uses streaming zip extraction (`yauzl`) with batched directory creation instead of `AdmZip`, and no longer skips writing regular files on component re-upload.
  * The Variables Synchronizer can now batch `sync()` per component instead of per partial. This behavior is configurable via `VARIABLES_SYNCHRONIZER_ENABLED` (default off).

## Bug Fixes

* **Fixed module cache miss that reloaded components from the database on every request** — A caching bug caused components to be re-downloaded from the database on each request (most visibly on `/auth`); they are now served from cache, significantly improving response times.
* **Fixed OAuth account testing with custom credentials** — Testing an account (`POST /accounts/:id/test`) that uses custom, user-level OAuth credentials now correctly resolves those credentials instead of falling through to missing system credentials. Auth module creation failures are now re-thrown during the auth callback so the user sees a real error instead of a false success, and `componentIds` is handled as both a string and an array.


---

# 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.6.md?ask=<question>&goal=<user_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.