Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to use lambda on chaining #687

Closed
dangollayan opened this issue Feb 5, 2024 · 6 comments
Closed

Unable to use lambda on chaining #687

dangollayan opened this issue Feb 5, 2024 · 6 comments
Assignees
Labels

Comments

@dangollayan
Copy link

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.

@dangollayan dangollayan added the bug label Feb 5, 2024
@fhoueto-amz
Copy link
Member

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

@dangollayan
Copy link
Author

any update on this?

@fhoueto-amz fhoueto-amz assigned jangidms and unassigned michaelin-96 Feb 15, 2024
@jangidms
Copy link
Member

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

Thanks

@dangollayan
Copy link
Author

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
Copy link
Member

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
Copy link
Member

bios6 commented Apr 1, 2024

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

@bios6 bios6 closed this as completed Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants