Independent study lab
This is an independent, free, learning-only student project. It respects every company and vendor. Trademarks belong to their owners. It is not affiliated with or endorsed by Amazon Web Services, Cisco, Genesys, Salesforce, Twilio, or any other company. If you have a concern, the page will be removed or corrected promptly through the contact form. Nothing here is sold. There are no ads. The author is happy to volunteer for any organization.
A flow log you can actually search — Learn it in 5 minutes
About five minutes of reading
The query is short. The discipline is saving the ContactId before you hang up the test phone.
Search for Error, for the block name, and for the ContactId. InvokeExternalResource is the Lambda block in the log. AccessDenied, timeout, and a response-shape failure look different if you read the Results field.
If the customer says the call died at the menu, you want the last block, not the first error you have ever seen in the log group.
- Turn logging on in a module if every flow should log.
- Retention of the log group is your setting.
- PII in attributes will land in the log. Do not log secrets.
- A successful block with a wrong branch is not an error. Read the attributes.
Number on this page: Key ContactId. Put it in the query first
Sources and go deeper
- Troubleshoot Lambda function failures in Amazon Connect | AWS re:Post community. last checked 2026-10
- Troubleshoot contact flow errors 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