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.
Lambda is a seam, not a place to hide a CRM — Learn it in 5 minutes
About five minutes of reading
The flow will not wait for a slow system of record. Design the function for the timeout you actually have.
Synchronous invoke waits at most 8 seconds. Asynchronous mode can be paired with a Wait of up to 60 seconds. A chain of Lambda calls in one contact must stay within 20 seconds.
Connect retries throttles and HTTP 500s, up to three times, until the block timeout. Your function should be safe to run twice.
- Add the function to the instance. An identity policy alone does not let the flow invoke it.
- Return a flat string map or JSON, matching the block. Nested objects fail a string-map block.
- Log the ContactId. The flow log has no Lambda RequestId to join on.
- Default block timeout is 3 seconds. Raise it on purpose, not by hoping.
Number on this page: Sync max 8s. Then Error or Timeout
Sources and go deeper
- 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
- Troubleshoot Lambda function failures in Amazon Connect | AWS re:Post community. last checked 2026-10
- AWS Lambda - Wikipedia Wikipedia. last checked 2026-10