Event Bridge Destination - Protocol Buffer Decode Error

We’re hitting a weird decode error on our Event Bridge destination - specifically, the Conversation.StateChanged event. It’s failing to parse the protobuf message, returning a gRPC status code of INVALID_ARGUMENT with a message about a missing field in the payload. At my last shop, we dealt with similar protobuf issues, but that was all homegrown tooling. This is hitting our production service mesh, and it’s not ideal.

The destination is configured to forward to a custom HTTP endpoint, and the flow itself is pretty vanilla - just the standard Architect state change event. We’re using the latest gRPC-Web SDK (v1.16.3) and the EventBridge integration is set up according to the documentation. INC-4471 flagged similar issues when we were testing with the PresenceChanged event, but that resolved itself after a GC platform update. The logs show the full payload is being sent, but the decode step in the Event Bridge service is choking. It’s almost like the protobuf definition has shifted slightly.

Okay, so that protobuf decode error-it’s almost always a version mismatch between what EventBridge expects and what Genesys Cloud is sending. Really common with the Conversation.StateChanged event, actually. Can you confirm what protobuf definition EventBridge is using? We’re on Genesys Cloud, so I’m guessing it’s not the latest. Also, what version of the gRPC library is your service mesh running? I’ve seen some older versions struggle with the schema evolution. It might be worth checking the Chrome DevTools network tab - see if you can grab a raw payload to inspect the field definitions.