> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/release-notes/august-2026/august-27.md).
# August 27
## :book-open: **New guide: When to build AI (and when to use AI to build)**
The **AI in Enterprise Integration** guide gives you a framework to decide when to build agentic workflows, when to stay deterministic, and when a hybrid approach is best.
It also covers how to use AI to build workflows (no matter where they live on the deterministic-to-agentic spectrum).
Spoiler alert: Claude Code isn't the answer ([but Digibee Digital Workers are!](/documentation/release-notes/digibee-digital-workers/now-in-early-access-digital-worker-mode.md)).
Download the guide
## :sparkles: **Agents**
### **Pipeline Key in Agent Logs**
You can now see the Pipeline Key directly in the Agent Logs table, alongside Timestamp, Agent Name, Agent Execution Key, Pipeline Name, and Content Preview. This brings Agent Logs in line with the standard Pipeline Logs table, so you can correlate any agent log entry with its specific pipeline.
Learn more
## :plug: **Connectors & Triggers**
### **Assume Role authentication for the SQS connector**
You can now authenticate the SQS connector using Assume Role, giving you a more secure way to connect across AWS accounts. This eliminates the need for long-lived static credentials and reduces the risk of credential exposure, while giving your security team tighter control over cross-account access.
Read the documentation
### **Native event routing**
Pipelines that publish and consume events now perform better: lower latency and higher throughput, especially under high event volume, with no changes required to your existing pipelines.
This change is being **rolled out gradually across realms**. Once it's active in your realm, if you redeploy the pipeline with [Event Publisher](/documentation/connectors-and-triggers/connectors/queues-and-messaging/event-publisher.md) without also redeploying the corresponding pipeline with [Event Trigger](/documentation/connectors-and-triggers/triggers/messaging-and-events/event.md), the platform displays an alert at deploy time. If you see it, redeploy the pipeline with Event Trigger as well, to keep timeout and redelivery settings aligned.
Learn more in [How to interpret event publishing and delivery alerts](/documentation/troubleshooting/deployment-issues/interpret-event-publishing-and-delivery-alerts.md).
## :bugs: **Bug Fixes**
The following issues were fixed in this release:
**Agents**
* **Agent Component:**
* Switching the model after configuring a JSON Schema cleared the schema, requiring users to set it up again.
* Switching to a model without custom temperature support (such as GPT-5.5) kept an old temperature value active and caused the request to fail; temperature now resets to the model's default automatically.
**Build**
* **Canvas:** Long path names on connectors like Choice overflowed their box; long names are now truncated with an ellipsis and shown in full on hover.
* **Pipelines:** Pipeline versions could link to the wrong project, causing them to disappear from the version list and selector even though they still worked normally.
**Connectors and triggers**
* **Connectors:** Disabling a field wouldn't automatically disable its dependent fields if they had already been enabled.
* **REST V2 connector:**
* The Body / Form Data field in the editor didn't always reflect the connector's saved configuration.
* The response body could return in Base64 even when Raw Mode was disabled.
* **Dynamics 365 connector:** The API URL failed to resolve global variables before validation, causing metadata discovery to fail even though pipeline execution worked normally.
* **Parallel connector:** Changing the Aggregation Type from Collate to Summary hid the button to add a connector to the flow, and deleting and re-adding a Parallel could disconnect previously connected steps.
* **API Trigger:** New routes added through the Routes List appeared disconnected from the Router on the Canvas.
**Platform**
* **Login:** The password reset form showed no error when the new password had already been used, leaving users unable to complete the reset.
* **Identity provider (IdP):** The "Created on" and "Modified on" dates didn't reflect each provider's actual creation and update dates.
* **Platform:** Confirmation modals could appear off-center or not respond to interaction over certain panels.
* **Header:** Fixed an issue where the Build, Run, and Monitor tabs in the new header couldn't be opened in a new browser tab; they can now be opened in a new tab as expected.
---
# 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, and the optional `goal` query parameter:
```
GET https://docs.digibee.com/documentation/release-notes/august-2026/august-27.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.