What is the standard pattern for handling persistent 5xx errors when consuming Genesys Cloud outbound webhooks?
We have a custom agent desktop service listening to routing.queueMember.update events. The integration works fine most of the time, but occasionally our endpoint returns a 503 due to a brief deployment window. Genesys retries the delivery, but if it fails again, the event is dropped. We need a reliable way to capture these failed deliveries for later processing.
Here is what we have tried:
- Configured the webhook in the Genesys UI with retry policy set to maximum.
- Added basic logging to the endpoint to capture the incoming JSON payload.
- Checked the
webhooksAPI documentation but didn’t see a direct “dead letter” endpoint.
The current response from our service looks like this when it fails:
HTTP/1.1 503 Service Unavailable
Content-Type: application/json
{
"error": "Service temporarily unavailable"
}
Is there a way to configure a secondary endpoint for failed deliveries? Or do we need to implement our own queue on the consumer side? We are using .NET 6 for the backend. The goal is to ensure no events are lost during these brief outages. Any code examples for handling this scenario would be appreciated. We want to avoid writing a custom retry mechanism if Genesys provides something out of the box.