# May 27

## **Release Notes 05/27/2025**

### **LLM Connector (General Availability)**

<figure><img src="https://content.gitbook.com/content/E9x0KHkAmxzJGlYPs9aE/blobs/QMA5EX1XaA8P5K3X2Lpd/LLM%20Connector.png" alt=""><figcaption></figcaption></figure>

**LLM Connector** is a new connector that sends requests to Large Language Models (LLMs) within Digibee pipelines, enabling tasks such as text classification, information extraction, summarization, and content evaluation.

It supports built-in authentication and works with major providers: [**Anthropic Claude**](https://www.anthropic.com/claude), [**DeepSeek**](https://www.deepseek.com/en), [**Google Gemini**](https://deepmind.google/models/gemini/), and [**OpenAI**](https://openai.com/). The configuration allows you to control model behavior, response format, and output structure based on your integration needs.

[Learn more in the documentation](https://app.gitbook.com/s/EKM2LD3uNAckQgy1OUyZ/connectors/ai-tools/llm).

### **Completed executions available for Data Streaming (General Availability)**

<figure><img src="https://content.gitbook.com/content/E9x0KHkAmxzJGlYPs9aE/blobs/TmmWbPmbtAYsS4hCDuYK/DataStreaming_ENG%20(1).png" alt=""><figcaption></figcaption></figure>

The **Data Streaming** feature (previously called Log Streaming) now allows you to stream log and completed execution data automatically to external tools of your preference. Save time by streamlining your analysis and connecting data across systems. Check out the [documentation](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/platform-administration/settings/data-streaming) and learn [how to configure Data Streaming with Datadog](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/platform-administration/settings/data-streaming/how-to).

### **Documentation production**

We have produced the following documentation:

#### **Best practices**

* [**Highly scalable ETL model for Digibee**](https://app.gitbook.com/s/aD6wuPRxnEQEsYpePq36/best-practices/highly-scalable-etl-model-for-digibee): An event-driven, scalable ETL model on Digibee for transferring large datasets from a relational database to a target system.
* [**JOLT and Double Braces on Digibee: Choosing the right method for data transformation**](https://app.gitbook.com/s/aD6wuPRxnEQEsYpePq36/best-practices/jolt-or-double-braces): Explore the advantages and use cases of both JOLT and Double Braces to help you choose the right option for your specific transformation needs.

### **Improvements and Bug fixes**

#### **Improvements**

* **Password confirmation for OAuth2-type accounts:** Accounts authenticated through an OAuth2 provider that has a certificate configured now require an authentication password. [Read the documentation](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/platform-administration/settings/accounts).

#### **Bug fixes**

* **Error deploying a pipeline larger than 1MB without displaying logs:** We fixed a bug that prevented error logs from being displayed when a pipeline larger than 1MB was deployed.
* **Error promoting multi-instance deployments:** We fixed a bug that caused a runtime error when promoting a multi-instance pipeline from the test environment to the production environment, preventing the operation from completing.
* **Error promoting a deployed pipeline in the Consumption realm:** We fixed a bug that caused an error when promoting a deployed pipeline from test to production, within the Consumption realm.
* **Error listing deployments on the Run page for projects with special characters in their names:** We fixed a bug that prevented projects containing the “&” character from being displayed correctly on the Run page after deployment.
* **Error displaying pipeline data in the Alerts side modal on the Monitor Overview page:** We fixed a bug that displayed empty or incorrect information when accessing the Alerts page through the Monitor Overview page.
* **`multiPartData` and `formData` not displayed in Execution Panel for REST V2 connector:** We fixed a bug that prevented `multiPartData` and `formData` from being displayed in the Execution Panel when the `Content-Type` was set to `application/x-www-form-urlencoded` or `multipart/form-data`.
* **Missing routes for REST API Trigger with Rate Limit enabled:** We fixed a bug that prevented route generation when the Rate Limit option was configured in the REST API Trigger. In some cases, the trigger was unable to properly process the defined request limit value.