> 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/02-09-26-release-notes-core.md). # 02/09/26 Release Notes (core) > **Release date:** 2nd September 2026 *** ## New Features {% embed url="" %} #### [**Platform Agents - Health Monitor Agent**](/product-documentation/ai/patchworks-ai-studio/platform-agents/health-monitor-agent.md) We've introduced a new Health Monitor agent that finds out why your flows are failing, without you having to trawl through run logs and version history yourself. When you ask about a failure, the agent reads across the flow's runs, logs, scripts and recent changes and returns a single diagnosis covering: * **The failure** - which flow failed, when, how many times, and whether it is still recurring * **Root cause** - the underlying reason, separated from the downstream errors it triggered * **What to investigate next** - where to look, including practical constraints such as payload retention * **A suggested fix** - a concrete change to the flow, which it can hand to the Implementation Agent to apply on your behalf *** #### [**Platform Agents - Documentation Agent**](/product-documentation/ai/patchworks-ai-studio/platform-agents/documentation-agent.md) A new Documentation agent writes and maintains the documentation for your integrations, so what a flow does is captured for your team rather than left as tribal knowledge. Point it at a flow and it generates a structured write-up covering the overview, trigger, data flow, and each shape in sequence with its purpose and key configuration. Documentation reflects the state of the flow at the time it is generated, and can be regenerated after changes or downloaded as a PDF to share. *** #### **Platform Agents - Migration Agent** A new Migration agent helps you move existing integrations onto Patchworks from another platform. Share what you have today - exports, specifications, mapping documents or a description of the current integration - and the agent analyses it, proposes the equivalent Patchworks connectors and flows, and works with the Implementation Agent to build them. You confirm the proposal before anything is created. The Migration agent is available via the Implementation Agent. *** #### [**Events - IBM MQ Support**](/product-documentation/connectors-and-instances/event-connectors.md) IBM MQ is now available as an event connector protocol, alongside AMQP. Event connectors, their queues/topics and listeners are now presented in a clearer, more consistent layout, making it easier to see at a glance what is connected, what is listening, and where any errors are occurring. *** #### [**Implementation Agent**](/product-documentation/ai/patchworks-ai-studio/platform-agents/implementation-agent.md) **- Multiple Flows & Flow-Independent Access** The Implementation Agent can now be used directly from the **Platform Agents** page, without needing to be inside a process flow first. Previously the agent's flow-building capability was only reachable from within a process flow. It now sits as a single top-level agent fronting Flow Builder, Connector Builder and Mapping, so you can start a conversation from AI Studio and let it decide which capability is needed. The agent can also create **multiple flows in a single request**. Describe an integration that needs several flows - for example an order sync, a fulfilment sync and an inventory sync - and it will propose and build each one, rather than requiring a separate conversation per flow. *** ## Improvements #### **AI Studio - Model Provider Failover** AI Studio agents now fail over automatically to a secondary model provider if the primary provider is unavailable, so agent conversations continue to work during an upstream outage. *** #### **Export Specific Flow Versions** Exporting a process flow was previously limited to the latest created version. You can now export any version of a flow. *** #### **Connector Builder - Import Mode Options on Creation** Import mode options are no longer shown on the initial create-connector screen, as they provided little context at that point in the setup. Import modes can still be configured once the connector has been created. *** #### **Run Logs - Item Counts on Active & Queue Tabs** The **Active** and **Queue** tabs on the run logs page now display the number of items in each, so you can see what's running and what's waiting without opening the tab. *** #### **Chat Menu Relocated to Top-Level Navigation** The chat menu has been moved out of the support section into the top-level navigation to make it easier to find. *** #### **Delete Confirmation - Name Must Be Typed** Copy and paste has been disabled in the delete confirmation field. The resource name must now be typed manually, restoring the safeguard the confirmation is intended to provide. *** ## Bug Fixes #### **Fix: Run Process Flow Shape Defaulting to a Flow Version** Resolved a regression where adding a Run Process Flow shape and selecting a flow pre-filled a version number, preventing "Use the latest deployed version of the flow" from being enabled until the version was manually cleared. Selecting the toggle now clears the version. *** #### **Fix: Backoff Time Not Saving in Connector Shape** Fixed an issue where the backoff time set on a connector shape was not saved unless Enter was pressed after entering the value. The value now saves as expected. *** #### **Fix: Slow Company Switching** Resolved an issue where switching between companies could take a significant amount of time for accounts with a large number of linked companies or resources. *** *For questions about this release, please contact the Patchworks support team or refer to the* [*product documentation*](https://doc.wearepatchworks.com/product-documentation)*.*