Hey everyone,
We’ve got a webhook endpoint listening to Genesys Cloud interaction events, specifically for wrapping up conversations. Lately, our server’s been throwing 502 Bad Gateway errors during peak loads. Genesys keeps retrying the delivery, which is fine, but after the retries exhaust, the event just vanishes. We need to capture those failed payloads so we don’t lose data.
Is there a way to configure a Dead Letter Queue (DLQ) or a secondary fallback endpoint directly in the Genesys Cloud webhook settings? I checked the /api/v2/webhooks docs, but I don’t see a field for a DLQ URI.
Here’s the JSON payload we’re trying to catch when it fails:
{
"id": "abc-123",
"event": "interaction.wrapped",
"data": {
"interactionId": "xyz-789"
}
}
If there’s no native DLQ support in the webhook config, what’s the standard pattern? Should we be building a middleware service that acknowledges the webhook immediately and then processes the async job, effectively acting as the buffer? That seems like a lot of overhead just to handle a 502.