Integrating Lambda function with API Gateway to interact with Slack more than once

DevOps AWS
1

Asking here but not sure if this is the right place… I am integrating a lambda function with api gateway to interact with slack via a slack. My code is working almost as expected. The result is correct and my lambda can send the message to slack via a http request with a slack webhook fine. The problem is that it I trigger it from slack sending the command that triggers my lambda… if I trigger it like more than once, only th efirst one works. I can see that my lambda receives the next requests and process it fine, and no errors on cloudwatch logs. If I send the command with a new string, it works fine, but if I repeat the same, it’s like slack webhook is refusing to send the same command within a minute or so

2

maybe this https://github.com/slackapi/bolt-python/issues/764#issuecomment-1312324756

3

although I’m not using bolt I believe…

4

this is weird to me… since when I send curl request to the same slack endpoint manually, via curl requests, it works no matter how many times…

5

but via lambda, it’s like if something weird is happening… if I send a different string, sure… it works… but repeating it… even after 30 seconds or more… it doesn’t send anything

6

actually, now that I am checking logs… it’s even before it tries to send the slack message… it’s my lambda that is not even executing the code when it’s the same parameters and string

7

Triggering from slack or via curl

8

I trigger my lambda via slack… I send my command via slack… what triggers my lambda via api gateway

9

for example: /my-command sned this

10

I send that via slack… it triggers my lambda and it works fine…

11

if I try again: /my-command send this

12

I see the lambda starts… but doesn’t run my functions…

13

but if I send /my-command send another

14

it runs the entire lambda with all the functions again…

15

if I repeat the same now: /my-command send another

16

the same happens, and it starts the lambda, but doesn’t run the functions…

17

but if I send a totally new one: /my-command send yetanother

18

so it’s like lambda seems to be the one not accepting repeated workload or something

19

I can see it starts, but doesn’t run all my functions inside that lambda… weird

20

when the lgos there should be way more, running all my stuff…