---
schema_version: "1"
id: 9dbb970f12d50a551093a894aa50e566fee7c51056a478c9073fb4864c876e25
title: gRPC Connector Release Notes
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/release-notes/connector/grpc-connector-release-notes-mule-4.md
canonical_url: https://docs.mulesoft.com/release-notes/connector/grpc-connector-release-notes-mule-4
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 1867343b85112140ce54f9996fcc7cb731ef0a8ba2bc16ec9f656f464703e636
description: MuleSoft Documentation Site
latest: true
---
---
product: Release Notes
version: master
---

# gRPC Connector Release Notes

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Connector for gRPC (gRPC Connector) enables you to connect to the gRPC API. gRPC Connector
enables Mule applications to communicate with gRPC services, providing both client and server
capabilities for high-performance, cross-platform RPC communication.

Guide: [gRPC Connector User Guide](https://docs.mulesoft.com/grpc-connector/latest/)

## 1.0.4

**September 7, 2026**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.11.0 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>17</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>When a gRPC server returned an error message containing non-ASCII characters, gRPC Connector displayed the raw percent-encoded bytes (for example, <code>%C2%A0</code>) instead of the actual text. Error messages with non-ASCII characters are now decoded correctly.</p></td><td><p>W-24045828</p></td></tr></tbody></table>

## 1.0.3

**August 31, 2026**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.11.0 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>17</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>gRPC Client connections to HTTP/2-only servers no longer silently fall back to HTTP/1.1, and connections configured with a custom TLS context no longer fail with <code>UNIMPLEMENTED</code>.</p></td><td><p>W-24021389</p></td></tr><tr><td><p>gRPC Server sources deployed on a domain-shared HTTP Listener no longer route requests to a disposed application after a hot redeployment, which previously caused <code>UNIMPLEMENTED</code>, <code>DEADLINE_EXCEEDED</code>, or <code>HTTP 408</code> errors.</p></td><td><p>W-24006480</p></td></tr></tbody></table>

## 1.0.2

**August 11, 2026**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.11.0 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>17</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>Inbound gRPC request metadata (headers) is now accessible to Mule flows through <code>attributes.headers</code> for the gRPC server sources. Header keys are lowercased, and header values aren’t logged to prevent credential leakage. For more information, see <a href="https://docs.mulesoft.com/grpc-connector/latest/grpc-connector-reference">gRPC Connector Reference</a>.</p></td><td><p>W-23556268</p></td></tr></tbody></table>

## 1.0.1

**July 31, 2026**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.11.0 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>17</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>gRPC server sources now return a configurable gRPC status code and description to the client through the <strong>Status Code</strong> and <strong>Description</strong> fields, instead of always returning <code>UNKNOWN</code>. For more information, see <a href="https://docs.mulesoft.com/grpc-connector/latest/grpc-connector-reference">gRPC Connector Reference</a>.</p></td><td><p>W-23537999</p></td></tr></tbody></table>

## 1.0.0

**March 18, 2026**

### What’s New

This is a new connector.

For more information, see the [gRPC Connector User Guide](https://docs.mulesoft.com/grpc-connector/latest/).

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.11.0 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>17</p></td></tr></tbody></table>

## See Also

- [gRPC Connector User Guide](https://docs.mulesoft.com/grpc-connector/latest/)

- [gRPC Connector Reference](https://docs.mulesoft.com/grpc-connector/latest/grpc-connector-reference)

- [Salesforce Help](https://help.salesforce.com/s/)

- [MuleSoft Services](https://www.mulesoft.com/support-and-services)

- [Known Issues](https://help.salesforce.com/s/issues)