- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
I had included a snippet of the Lambda log here is a complete event as requested
START RequestId: 9e70f9f2-9887-40c1-9e97-af737f403946 Version: $LATEST
2022-04-03T21:19:59.330Z 9e70f9f2-9887-40c1-9e97-af737f403946 INFO UI = undefined
2022-04-03T21:20:00.024Z 9e70f9f2-9887-40c1-9e97-af737f403946 INFO MessageID is f66bb97a-3ed9-59bc-8488-e3be2f667a79
2022-04-03T21:20:00.062Z 9e70f9f2-9887-40c1-9e97-af737f403946 INFO Server response function
END RequestId: 9e70f9f2-9887-40c1-9e97-af737f403946
REPORT RequestId: 9e70f9f2-9887-40c1-9e97-af737f403946 Duration: 734.42 ms Billed Duration: 735 ms Memory Size: 128 MB Max Memory Used: 78 MB Init Duration: 417.37 ms
When you're testing the Lambda are you using the right JSON string that mimics what Connects sends? I don't see where you get the right JSON parameter, I suspect that's the issue.
The Connect log seems to show that it is sending: "FunctionArn": "arn:aws:lambda:us-west-2:507182563096:function:RHCS-VID-SMS", "Parameters": { "key1": "707777" }, "TimeLimit": "3000" } } Key1 would be correct and the target variable UI is defined console.log("UI = " + event.key1).
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 3 Jahren