--- schema_version: "1" id: 1f38942dad68d56592119bfae17337e9eab33b744e737552bbd3ffa90de6fb59 title: gRPC Connector Release Notes collection: mulesoft version: current locale: ja-jp portal_url: https://docs.salesforce.com/mulesoft/current/ja-jp/release-notes/connector/grpc-connector-release-notes-mule-4.md canonical_url: https://docs.mulesoft.com/jp/release-notes/connector/grpc-connector-release-notes-mule-4 source_site: docs.mulesoft.com content_type: documentation content_hash: 62488d7d07476130a9060187adb763e549dd959ffa363362c3dca429f324f17a description: MuleSoft Documentation Site latest: true --- # gRPC Connector Release Notes 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)1.0.4 **September 7, 2026** ### Compatibility
Software Version

Mule

4.11.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

When a gRPC server returned an error message containing non-ASCII characters, gRPC Connector displayed the raw percent-encoded bytes (for example, %C2%A0) instead of the actual text. Error messages with non-ASCII characters are now decoded correctly.

W-24045828
## [](#1-0-3)1.0.3 **August 31, 2026** ### Compatibility
Software Version

Mule

4.11.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

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 UNIMPLEMENTED.

W-24021389

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 UNIMPLEMENTED, DEADLINE_EXCEEDED, or HTTP 408 errors.

W-24006480
## [](#1-0-2)1.0.2 **August 11, 2026** ### Compatibility
Software Version

Mule

4.11.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

Inbound gRPC request metadata (headers) is now accessible to Mule flows through attributes.headers for the gRPC server sources. Header keys are lowercased, and header values aren’t logged to prevent credential leakage. For more information, see gRPC Connector Reference.

W-23556268
## [](#1-0-1)1.0.1 **July 31, 2026** ### Compatibility
Software Version

Mule

4.11.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

gRPC server sources now return a configurable gRPC status code and description to the client through the Status Code and Description fields, instead of always returning UNKNOWN. For more information, see gRPC Connector Reference.

W-23537999
## [](#1-0-0)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
Software Version

Mule

4.11.0 and later

OpenJDK

17
## [](#see-also)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)