# May 15, 2026 - 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>

* **Crate Marketplace**
  * Added an “Attention Needed” integration state to crate details pages when health checks detect broken configurations.
* **Onboarding**
  * Sorted onboarding checklist crates by use case complexity to guide MSPs toward easier early wins.
* **RoboRewsty**
  * Added context compacting to avoid max context errors.
* **Workflow Builder**
  * Closed the Action Settings pane automatically when deleting tasks in the new workflow canvas.

</details>

<details>

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

* **Integrations**
  * Fixed Microsoft Graph user actions to stop defaulting blank usage locations to US.
  * Normalized crate category casing so the marketplace shows a single Financial Management category.
  * Fixed ConnectWise ASIO paginated requests to return all available results instead of stopping at 100 items.
  * Fixed OAuth authorization popups in custom integrations.
* **Workflow Builder**
  * Fixed workflow version history crashes by correctly displaying “Deleted User” for changes made by removed users in the new canvas view.
  * Fixed array input fields to show and allow editing of Jinja values in the new canvas.
  * Fixed target workflow autocomplete to filter matching workflows immediately while typing in trigger settings.

</details>

<details>

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

* Check back soon!

</details>


---

# 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.rewst.help/updates/development-updates/2026-dev-updates/may-15-2026-dev-update.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.