> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/releases/2025/2025.25.0-december-17-2025-preview-release.md).

# 2025.25.0 - December 17 2025 Preview Release

Changes are scheduled to go to production on January 7 2026

## Improvements & Bug Fixes

* **Categories -** Fixed an issue where large sets of Categories would cause 500 level errors.
* **Fast Compositor** - Fixed an issue where some intermittent 500 level errors were thrown by the server due to too many concurrent requests. Implemented a more robust queue to properly await for the available resources to process the requests.
* **Metadata Query** - Fixed an issue with the Logic Editor UI where it appeared that Metadata Query rules would get broken when editing them or cloning assets in some cases.&#x20;


---

# 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://community.threekit.com/releases/2025/2025.25.0-december-17-2025-preview-release.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.
