> 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/september-2026/september-9.md).
# September 9
## :sparkles: **Agents**
### **Per-model validation for Max Output Tokens**
The **Max Output Tokens** field in the Agent Component now validates against each model's own limit instead of a single fixed range for all models. If you enter a value outside the accepted range, the field shows an error message with the correct range for the selected model, helping you catch configuration mistakes before deployment.
Read the Agent Component documentation
## :rocket: **Platform Improvements**
### **Pipeline warnings are back in Run**
You can once again see warnings on pipeline cards in Run when common issues occur, such as configuration changes, memory limits, or deployment problems. Hover over the warning icon for a quick summary, or open the pipeline details for the full description and recommended action.
See how to resolve pipeline issues
### **Table sorting improvements in Monitor**
You can now sort the [Executions table](/documentation/developer-guide/development-cycle/dashboards/completed-executions.md) in Monitor by **Elapsed Time**, in ascending or descending order, by clicking the column header. The default sort remains by Timestamp. This sorting applies across the full search result, not just the Executions currently loaded on screen.
Sorting in the [Overview table](/documentation/developer-guide/development-cycle/dashboards.md)'s pipelines list now also applies across the full result set, not just the page currently loaded. Previously, sorting only affected the visible page, which could make the order look inconsistent when paginating.
See what you can view in Monitor
## :plug: **Connectors & Triggers**
### **Dynamic account resolution for the SQS connector**
You can now resolve the SQS (AWS) connector's account dynamically at runtime instead of only at design time. Turn on **Use Dynamic Account** to replace the static Account field with an Account Name field that accepts functions and globals, so a single pipeline can target queues in different AWS accounts, for example across environments or tenants, based on a value resolved by a Store Account step. Existing pipelines are unaffected, since the option defaults to off.
Read the SQS connector documentation
### **Reply To field in the Email V2 connector**
You can now set a **Reply To** address on the Email V2 connector, so recipient replies go to a designated mailbox instead of the From address. The field accepts a single address or a comma-separated list, and can be driven by pipeline variables. Leaving it empty keeps the current behavior unchanged.
Read the Email V2 connector documentation
## :bugs: **Bug Fixes**
* **Linter:** Fixed an issue where a step could be incorrectly flagged with a "Double braces alias in use, but it was not found at any previously connected component" error when the alias was only mentioned in the step's Documentation field, without being wrapped in Double Braces (`{{ }}`).
* **Capsules:** Fixed an issue where the icon selection field was missing from the capsule creation form, restoring the ability to choose an icon for a capsule.
* **Test Case:** Fixed an issue where clicking the Single Run option left the Results tab empty for subsequent executions, including via the Execute button in the Execution Panel.
---
# 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/september-2026/september-9.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.