> For the complete documentation index, see [llms.txt](https://help.watcherlink.online/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.watcherlink.online/release-notes/release-note-1.45.0.md).
# Release note 1.45.0
We're excited to present Moonone, focused on expanding tax module capabilities, improving notification stability, and accelerating interface performance.
### 1. Tax Report Regeneration
You can now regenerate tax reports with updated details. When regenerating after a report has been marked as submitted, the correction number increments automatically. A new "Version and update date" column has been added to the reports table for tracking change history.
### 2. Faster Page Loading
Data loading during navigation has been optimized — pages now open significantly faster thanks to caching and reduced server requests.
### 3. Bug Fixes
* Improved notification delivery stability — connection now auto-recovers seamlessly.
* Fixed a bug where, upon first opening the task creation window, the options in the reason selection drop-down menu were not displayed.
* Stop factors no longer block automatic reason detection for tasks.
* Export file now displays the unit of measurement for Power Consumption.
---
# 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.watcherlink.online/release-notes/release-note-1.45.0.md?ask=&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.