# Features / Improvements & Fixes

## Improvements :muscle:

### Provisioning API in OpenAPI

The Provisioning API is now documented in the OpenAPI specification.

### Logging

* **`TopicStatsWorker` log noise** during normal operation has been demoted from `INFO` to `DEBUG`, so production logs stay readable.
* **Better diagnostic logging for topic identification** when investigating JSON payload edge cases.

## Fixes 🛠️

### SQL on partial JSON payloads

When a SQL query joined or selected from a topic whose value was a JSON object missing some fields, the engine could fail to resolve a union struct type. The engine now matches by **subset** of fields instead, so partial JSON objects no longer fail the query.

### Topics with unresolved Schema Registry references stay readable

If a topic's value or key referenced a schema that the agent could not yet resolve from the Schema Registry (for example during startup or when the registry was briefly unreachable), reads against that topic could fail. Marshaller construction is now deferred, so the rest of the topic remains readable while the registry catches up.

### Schema listing no longer shows "NaN"

The Schemas listing in the Agent UI no longer renders "NaN" in place of a name when a schema lacks a numeric identifier.

### Topic configs page adapts to small viewports

The topic configurations screen now lays out correctly on smaller screen sizes and viewports.


---

# Agent Instructions: 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:

```
GET https://docs.lenses.io/latest/changelog/lenses-agent/6.2.1/features-improvements-and-fixes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.