> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/release-information/core-release-notes/03-06-26-release-notes-core.md).

# 03/06/26 Release Notes (core)

> **Release date:** 3rd June 2026

***

### New Features

#### [AI Studio - Platform Agents](/product-documentation/ai/patchworks-ai-studio.md)

A set of intelligent agents built directly into Patchworks, designed to do the heavy lifting of integration for you.

This release marks the first phase of AI Studio - introducing Platform Agents with the Implementation Agent, which lets you build process flows and generate schema mappings through natural language prompts.

***

#### [Platform Logs (formerly Audit Logs)](/product-documentation/general-settings/platform-audit-logs.md)

A new **Logging** page replaces the previous audit log experience. Logs are have been improved for faster search and improved scalability, organised into four levels:

| Level      | On by default | Retention | What's captured                                                        |
| ---------- | ------------- | --------- | ---------------------------------------------------------------------- |
| **Audit**  | ✅             | 90 days   | Logins, password changes, user/role/permission changes, API key events |
| **Change** | ✅             | 90 days   | Flow, connector, mapping, and scheduler changes                        |
| **Error**  | ✅             | 90 days   | Failed saves, permission denied events, validation errors              |

**New capabilities on the Logging page:**

* Tabbed display by log level (Debug tab only appears when debug logs exist within the selected date range)
* Full-text search to filter log content
* Group by date, event, company, or user
* Date range filtering
* Export all logs matching the current query
* Expandable log entries for full detail
* Company selector for users with managed companies
* Configurable log retention per company upon request
* Alerting -assign notification groups to specific log levels so admins are notified when errors occur

Coverage has also been expanded to capture all important events, including: user account actions, login events, role and permission changes, company tier changes, flow deployments, VE publishing, and connector instance changes.

***

#### [Raw JSON Trigger Endpoints](https://doc.wearepatchworks.com/product-documentation/api-reference/flow-actions/flows#post-api-v1-flows-flow_id-manual-raw-version_id)

New `/raw` variants of the flow trigger endpoints are now available. These accept a standard JSON payload directly - no need to wrap the body in a `payload` string field. The existing endpoints are unchanged for backwards compatibility.

Available for: **webhooks**, **start**, **manual**, and **callback** triggers.

**Existing endpoint (unchanged):**

json

```json
{
    "payload": "{\"ORDER\": \"#LMUK62388\"}"
}
```

**New `/raw` endpoint:**

json

```json
{
    "ORDER": "#LMUK62388"
}
```

***

#### [Log Level Alerting](https://doc.wearepatchworks.com/product-documentation/general-settings/platform-audit-logs#h-alerts)

Alerts can now be configured based on log levels. Assign notification groups to Audit, Change, Error, or Debug log levels so the right people are notified automatically when matching events occur.

***

### Improvements

#### Guard VE-Dependent Entities from Deletion

Entities actively referenced by a Virtual Environment (VE) are now protected from deletion. Attempting to delete one will return a clear error, preventing broken VE configurations.

***

### Bug Fixes

#### Fix: VE Delete Confirmation Modal Not Closing

After confirming deletion of a VE, the confirmation modal was remaining open even though the deletion was successful. Repeatedly submitting the modal would then delete subsequent VEs. The modal now closes correctly after a successful deletion.

***

#### Fix: Flow Runs - Filter Label Missing

A label was missing from the filters on the Flow Runs page, making certain filter options unclear. This has been corrected.

***

#### Fix: Flow Label Priority Order

The order in which flow labels are displayed has been corrected to follow the expected priority ordering.

***

#### Fix: Cloned Endpoint Default Name Contains Invalid Characters

When cloning an endpoint, the default name was generated by appending `(1)` to the original name. Since brackets are not permitted in endpoint names, this prevented saving without manually editing the name first. Cloned endpoints now default to a valid name.

***

*For questions about this release, please contact the Patchworks support team or refer to the* [*product documentation*](https://doc.wearepatchworks.com/product-documentation)*.*


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.wearepatchworks.com/product-documentation/release-information/core-release-notes/03-06-26-release-notes-core.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.