Track
Lambda
Most 'random' flow errors are a Lambda response that missed the timeout or the shape Connect accepts.
3 rooms. Open one, then use its quiz.
The response contract
Connect does not debug your function. It branches.
When the work is slower than eight seconds
Silence is a defect. Async plus a prompt is the pattern.
Association, resource policy, and the log that says AccessDenied
The flow log is telling the truth. The function never ran.
Sources and go deeper
- Troubleshoot Lambda function failures in Amazon Connect | AWS re:Post community. last checked 2026-10
- Flow block in Connect Customer: AWS Lambda function - Amazon Connect Customer AWS docs. last checked 2026-10
- What is AWS Lambda? - AWS Lambda AWS docs. last checked 2026-10
- AWS Lambda - Wikipedia Wikipedia. last checked 2026-10
sources.json (lambda-contract) sources.json (lambda-async) sources.json (lambda-perms)