> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/updates/development-updates/2025-dev-updates/december-19-2025-dev-update.md).

# December 19, 2025- Dev update

Explore what new changes the Dev team has deployed in the last week.

This can be anything from new features, bug fixes, or QoL changes!

<details>

<summary><strong>New features and items</strong></summary>

* Check back next week!

</details>

<details>

<summary><strong>Bug fixes and chores</strong></summary>

* **Integrations**
  * Improved Datto Autotask PSA integration error messaging and clearly require the API Tracking Identifier to prevent authentication failures.
  * Fixed Pax8 OAuth token refresh failures by clearing client ID and secret after successful OAuth authorization to prevent conflicting credential modes.
  * Investigated and resolved an unintended spike in Halo PSA “New ticket record” trigger executions in Prod-UK to prevent excessive and duplicate workflow activations.
* **Workflows**
  * Fixed boolean workflow task parameter sizing to ensure full-width alignment and consistent layout across related input fields.
  * Expanded S3 dehydration to all serialized fields with a database fallback to improve durability and reduce Postgres storage.
* **RoboRewsty**
  * Fixed RoboRewsty follow-up conversation failures so users can continue chats after the first message without errors.
* **General**
  * Added adaptive rate limiting and startup jitter to database notification reprocessing to prevent queue flooding and cascading pod failures during engine restarts.
  * Configured Redis task TTL via an environment variable to control task result key retention and reduce memory growth.

</details>

<details>

<summary><strong>Coming soon</strong></summary>

* Connectwise Asio integration

</details>


---

# 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.rewst.help/updates/development-updates/2025-dev-updates/december-19-2025-dev-update.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.