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

# December 2025

### December 4, 2025

#### [Reports](https://docs.perkville.com/features/reports.md)

* Updated all reports to no longer show an error when refreshing the page after submitting a report.
* Added columns for each progress activity in the [Challenge Progress by Individual](https://docs.perkville.com/features/reports/challenge-progress-by-individual.md) report. Removed the "Requirements Completed" column from this report.
* Added the Challenge Name to the Challenge Progress by Individual and [Challenge Requirements ](https://docs.perkville.com/features/reports/challenge-requirements.md)reports.
* Fixed an issue where some challenge report pages misrepresented which challenge the report was ran for.

### December 11, 2025

#### [Reports](https://docs.perkville.com/features/reports.md)

* Added the ability to specify the timezone in which reports should be run.
* Fixed an issue that sometimes caused an incorrect redirect after submitting a report.
* [Transaction Detail](https://docs.perkville.com/features/reports/transaction-detail.md)
  * Updated the Earn/Redeem perk filters to include Adjustment type perks.
* Some minor UI updates.

#### [Customer details](https://docs.perkville.com/features/customers.md#accessing-a-customers-profile)

* Added some additional clarification on the Created/Transaction date columns

#### Dashboard

* Some minor UI updates.


---

# 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.perkville.com/overview/release-notes/december-2025.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.
