> 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-11.md).
# August 11
## :sparkles: **Agents**
### **Test case creation inside the Pipeline Logs page**
You can now turn an agent execution into a test case with one click, directly from the execution details in the Agents tab of Pipeline Logs. The test case is saved to a dataset with pre-filled variables already mapped, so you don't need to build a test scenario from scratch.
This makes it easier to validate agent behavior, troubleshoot issues, and reuse real interactions in your next evaluation run.
See how it works
### **Increased default timeout on the MCP Server Trigger**
The default timeout for the MCP Server Trigger increased from 30,000ms to 90,000ms, reducing the chance of timeouts on longer-running tool executions. You can still edit this value if your use case needs something different.
Learn more
## :rocket: **Platform Improvements**
### **UI update on Monitor Overview**
The chart on the Monitor Overview page has a refreshed UI, and you can now zoom in directly on the chart. This update makes it easier to analyze specific spikes and trends.
Read the documentation
### **Current month balance now visible before invoice closes**
If you're on the Consumption Based Model and have usage beyond your contracted limit, you can now see this in the Invoice History table before the invoice closes.
The current month appears at the top of the table with an Open badge, since open invoices may change until the month closes.
Learn more
## :plug: **Connectors**
### **OData and Dynamics365 Finance & Operations connectors**
Two new connectors are now available, extending the platform's REST engine to OData-compliant services and to Microsoft Dynamics 365 Finance & Operations.
* **OData:** Connects you to any OData-compliant service (v4 or v2), such as SAP, Microsoft Dynamics 365, Business Central, Salesforce, and public OData feeds, with support for CRUD operations, query options like filter and expand, actions and functions, and batch requests.
* **Dynamics 365 Finance & Operations:** Reads and writes Microsoft Dynamics 365 Finance & Operations' public OData data entities directly from your pipelines, with support for CRUD, cross-company access, and batch requests.
Learn more in the [**OData**](/documentation/connectors-and-triggers/connectors/web-protocols/odata.md) and [**Dynamics 365 Finance & Operations**](/documentation/connectors-and-triggers/connectors/enterprise-applications/dynamics-365-finance-and-operations.md) documentation.
## :bugs: **Bug Fixes**
* **Stream CSV Reader:** Fixed an issue where the Skip and Limit fields only accepted numeric values. They now also accept Double Braces expressions.
* **Canvas:** Fixed an issue where the cursor jumped back to the beginning of the field while typing in fields that auto-format content, such as payload fields in the Execution Panel and the AI Assistant's Input and Output fields for connectors.
---
# 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-11.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.