Context:
Running into a weird bug with our AWS EventBridge integration designed to ingest real-time Genesys Cloud events. We have configured the EventBridge Rule with a precise event pattern matching source: "genesys.cloud" and detail-type: "Interaction Created". The rule triggers successfully, and the target Lambda executes without error. However, the detail object in the EventBridge payload is significantly truncated compared to the full interaction object documented in the Genesys Cloud API v2 specs.
Question:
Is there a specific configuration in the Genesys Cloud Event Streams or the EventBridge partner integration that controls the depth of the payload? We are observing a 200 OK response from the webhook endpoint during setup, yet the runtime data lacks critical attributes like wrap-up-code and skill-group assignments. Has anyone encountered this serialization limitation when mapping Genesys Cloud events to EventBridge?