> 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/october-2026/october-6.md).

# October 6

## <i class="fa-rocket">:rocket:</i> **Platform Improvements**

### **Instance variables in the Account field**

In multi-instance pipelines, you can now set the Account field to an instance variable directly on the canvas, in both connectors and capsules. This means a single pipeline can authenticate with different credentials for each instance, such as one account per client or region, without duplicating the pipeline or editing the flowSpec by hand. Click the { } button next to the Account label and enter a variable, such as {{replica.account-name}}.

<a href="/documentation/platform-administration/settings/multi-instance.md#use-a-different-account-for-each-instance" class="button primary">Learn how to configure Multi-Instance pipelines</a>

<figure><img src="https://4091659634-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE9x0KHkAmxzJGlYPs9aE%2Fuploads%2FnvS3i8uJp7YGntvlYcSS%2FMulti-Instance%20Accounts.gif?alt=media&amp;token=5f085429-e9a6-4f9c-ac11-0861ee6eae52" alt=""><figcaption></figcaption></figure>

### **Globals page redesign**

The Globals page now has the same layout as the Accounts page, which makes globals easier to find and manage. Filter globals by category or deprecation status, identify deprecated globals by the tag next to their names, and see how many deployed pipelines use each global in the new Running Pipelines column.

<a href="/documentation/development-cycle/build-overview/globals.md" class="button primary">Explore the Globals documentation</a>

## <i class="fa-plug">:plug:</i> **Connectors & Triggers**

### **MCP Server Trigger supports MCP revision 2026-07-28**

The MCP Server Trigger now supports revision 2026-07-28 of the Model Context Protocol (MCP), alongside the revisions it already supported. AI agents and MCP clients that use the new revision can call your tools on the same endpoint, while clients on earlier revisions keep working without changes. You don't need to reconfigure or redeploy your pipelines.

<a href="/documentation/connectors-and-triggers/triggers/web-protocols/mcp-server.md" class="button primary">Check the MCP Server Trigger documentation</a>

### **Certificate validation for SQL Server in DB V2**

DB V2 now validates SQL Server certificates issued by a custom or private certificate authority. Use the new **SQL Server Truststore** parameter to select the Certificate Chain account with the CA certificates for the connection, with support for both static and dynamic accounts.

<a href="/documentation/connectors-and-triggers/connectors/structured-data/db-v2.md" class="button primary">Set up certificate validation in DB V2</a>

### **Total iteration time limit for Object Store queries**

The Object Store connector has a new **totalTimeoutMs** parameter that sets a time limit, in milliseconds, for the entire read in the Find by Object ID, Find by Query, and Aggregate operations. While **queryTimeoutMs** limits only the initial query, **totalTimeoutMs** also covers every batch fetched from the cursor and retries. This prevents queries that return many documents from streaming results for hours and keeping the step busy.

<a href="/documentation/connectors-and-triggers/connectors/structured-data/object-store.md" class="button primary">See all Object Store connector parameters</a>

## <i class="fa-bugs">:bugs:</i> **Bug Fixes**

* **Canvas:** Fixed an issue where connector details didn't reappear after zooming in, didn't hide after zooming out, and could be missing when opening another pipeline.
* **Accounts:** Improved the error message for Google Key accounts with an invalid key, which now includes the account name so you can easily identify which account needs to be fixed.
* **Consumers:** Fixed an issue where consumers (API keys) associated with more than about 100 pipelines behaved inconsistently: pipelines could appear in the list but fail when called, saving the consumer without changes could remove associations, and removing an association could fail.
* **Pipeline:** Fixed an issue where saving a pipeline to generate a new version could fail with a 409 error due to duplicate version records.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digibee.com/documentation/release-notes/october-2026/october-6.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.