Troubleshooting tree
Pick the symptom, then the capture. Change one thing.
- No audio, agent shows Available Microphone permission, then UDP 3478, then VPN on the media path. Lab: webrtc.
- ice_collection_timeout DNS for TurnNlb from that PC. Lab: webrtc.
- Flow error and an empty Lambda log Association and the Lambda resource policy. AccessDenied never reaches your function. Lab: lambda-sim.
- Lambda log is fine and the flow took Error Response shape or the 8-second wait. Lab: lambda-sim.
- Caller hears silence and the contact ends An error branch is not connected. Read the flow log for that ContactId. Lab: flow-log-reader.
- Wrong queue answers Priority and delay on the profile, not the queue name. Lab: routing-designer.
- Recording missing Block enabled, bucket policy, key policy, then one new test call. Lab: find-fault.
- CTR missing after a minute Wait. Five quiet minutes is the point to read Firehose errors. Lab: ctr-inspector.
- Screen pop is the wrong person ANI matched a household. Pop the account id the flow collected. Lab: ecosystem-map.
- WFM adherence is blank One agent event, a status map, and a published schedule. Lab: wfm-adherence.
- 911 would reach headquarters The stored profile address is stale. Validate, store, test with 933. Lab: e911-checker.
Source: re:Post, flow errors
Sources and go deeper
- Troubleshoot contact flow errors in Amazon Connect | AWS re:Post community. last checked 2026-10
- Troubleshoot Lambda function failures in Amazon Connect | AWS re:Post community. last checked 2026-10
- How Contact Control Panel (CCP) uses WebRTC - Amazon Connect Customer AWS docs. last checked 2026-10
- RFC 5766: Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN) | RFC Editor RFC. last checked 2026-10
- WebRTC - Wikipedia Wikipedia. last checked 2026-10