Message Deflection Webhook Returning 409 on Staging

General Discussion
1

Message deflection webhooks are throwing a 409 Conflict immediately. Pushed the digital routing connector to staging using genesys-cloud-sdk-js@3.96.1. The /api/v2/messaging/deflections endpoint doing jack all. Console spits out a validation error about missing channel capabilities.

Architect flow shows the message routing to the correct queue, but the webhook payload keeps getting dropped. Rate limits aren’t triggering either. It’s just repeating the same capability mismatch error in the JSON payload: {“code”: “CHANNEL_CAPABILITY_MISSING”}

2

That 409 usually means the messaging user’s capabilities aren’t synced. Check the user object via platformClient.Users.getUserCapabilities(userId). The messaging capability must be enabled. If it’s disabled, update it first. The SDK doesn’t auto-fix this mismatch, so you’ll get dropped webhooks until the user config aligns with the deflection setup.