- Newest
- Most votes
- Most comments
There is no direct access to the error details hence a block returns an error condition from the Contact Flow. Depending on your use-case you may want to ensure you have Logging enables on your Contact Flow and handle the error message from the CloudWatch Log which is being created for every contact. When calling the Lambda you can reference the ContactID to find the right log stream for that.
See more information on Best Practices for Amazon Connect and Track Events as customers interact with flows .
Yes, I know that there is an error inside logs and I also know that we can create subscription filter for log group and invoke lambda from there. But the problem is that this log entry does not contains any information about contact attributes such as user defined attributes, system etc. only contactId. We have to search across all log entries with this contactId to find some usefull information.
Relevant content
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
+1 (CFBR)
It would be great to have!