Hey folks,
We’re hitting the ceiling on our Lambda concurrency during peak hours. Genesys Cloud is firing a ton of conversation.update events through EventBridge, and our handler can’t keep up. We get 429s back from the platform when the queue backs up.
Is there a way to batch these requests on the Lambda side, or should we be tuning the provisioned concurrency? Here’s the basic trigger setup:
{
"source": ["genesys.com"],
"detail-type": ["Conversation Event"]
}
Any tips on handling the volume?