aws-solutions / qnabot-on-aws

AWS QnABot is a multi-channel, multi-language conversational interface (chatbot) that responds to your customer's questions, answers, and feedback. The solution allows you to deploy a fully functional chatbot across multiple channels including chat, voice, SMS and Amazon Alexa.
https://aws.amazon.com/solutions/implementations/aws-qnabot
Apache License 2.0
401 stars 253 forks source link

Unable to use lambda on chaining #687

Closed dangollayan closed 8 months ago

dangollayan commented 9 months ago

When using a lambda in chaining, it doesn't go with the document chain image

As I've checked the code evaluateConditionalChaining, there is invokeLambda function where the return is an array that includes req, res, and payload image

but upon checking the invokeLambda function it only returns req and res image

I think this is the reason why it doesn't get the payload, because it doesn't return the payload in the invoke lambda function.

Kindly validate if my assumption is correct.

fhoueto-amz commented 9 months ago

Thanks for reporting this. We will review and revert to you.

dangollayan commented 9 months ago

any update on this?

jangidms commented 9 months ago

Hi @dangollayan Your assumption is correct. Thanks for reporting this. We'll plan a fix for this issue.

Thanks

dangollayan commented 9 months ago

HI @jangidms , while I wait for fix, can you guide me where should I apply the fix on the code in the deployed qna bot?

I tried updating the Es-Proxy layer image image and set all the function to use the new version image

but still it didn't reflect on our end.

jangidms commented 8 months ago

Hi @dangollayan You can follow below steps to update Fulfillment lambda to use updated Esproxy layer.

  1. Download the Esproxy layer
  2. Make changes to Esproxy layer and upload updated layer zip file
  3. From Fulfillment lambda, under Code -> Layers -> Edit Esproxy layer version to be latest
  4. From Fulfillment lambda -> Version -> Publish new Version
  5. From Fulfillment lambda -> Aliases -> Edit live alias to point it to new lambda version

Please let me know if you have any further questions

Thanks

bios6 commented 8 months ago

Hi @dangollayan this issue should be resolved with the latest release v5.5.1. Thank You!