> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.3/whats-new/release-6.0/patch-6.0.1/patch-6.0.1.2.md).

# Patch 6.0.1.2

The patch 6.0.1.2 sharpens everyday workflows across Kaiya, Vizpads, and data prep. You’ll see faster Kaiya rendering, accurate load progress and smoother metric switching (including maps).

## **🛠️** Minor fixes

1. Resolved an intermittent SAML SSO redirect error so that logins now reliably route to the correct page, with a safe fallback to Home.
2. In Kaiya, resolved an issue where, in some sessions, answers didn’t appear in the chat until a page refresh. Messages now render instantly as they arrive.
3. In Vizpads, resolved a rare error (*“Something went wrong”*) due to a version mismatch.
4. In Vizpads, improved platform reliability and reduced intermittent failures during content rendering.
5. In Vizpads, fixed an issue where control filters could appear duplicated, especially after cloning tabs or reopening unsaved changes.
6. In Vizpads, fixed the loading progress bar so it now tracks chart rendering accurately and dismisses itself once everything finishes, especially if you switch tabs, apply multiple filters, or change custom views mid-load.
7. In the scatter charts of Vizpads, fixed a rare failure that blocked Vizpads from saving after edits (rename, clone, type switch, or filters).
8. In Vizpads, cloning a Vizpad tab now preserves all **Switch Metric** settings: enabled state, selected/available measures, and the default metric.
9. Calculated Columns now preserve your exact null logic. You can explicitly choose how to handle nulls (preserve, replace with 0, or custom), ensuring metrics like "*Gross Sales"* match your warehouse results.
10. Under **Data → Scripted Datasets**, fixed an issue that could occur when validating SQL changes on datasets with downstream dependencies. Validation errors now display inline without closing the editor, so you can review issues and continue editing without losing work. Overall stability is improved when columns are renamed/removed, reducing interruptions during pipeline authoring.
11. In Notifications, fixed an intermittent error that could appear after switching between browser tabs and returning to the **Notifications** page.
12. In the control filters of Vizpads, fixed an issue where **Available** values didn’t populate in **Edit** mode after reload.
13. Under **Data → Business Views**, restored support for *“source column name”* mappings so charts resolve fields correctly even when dataset column names change.
14. In Vizpads, fixed the issue with switching measures on the fly in heat maps, boundary maps, and location maps.
15. In Vizpads, resolved an issue where charts didn't show a *“No data found. Please modify the current configuration or filters”* message when filters return zero rows.


---

# 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://help.tellius.com/tellius-6.3/whats-new/release-6.0/patch-6.0.1/patch-6.0.1.2.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.