by the way… the same happens if I try a previously one… for example… saying I ran with string1
, after that with string2
, after that with string3
…
and I try again with any of those 3… the same happens… so it will only work fully if I now try with another one… like string4
Don’t you have to ack() the slack commands?
hum… don’t know… first time trying this… what do you mean with that?
I believe you are supposed to reply to slack with “I got this message” somehow when they use slack commands. Sending a response from your bot doesn’t count. I’m not super clear because I haven’t done this in a long time and it looks like things have changed but it appears you are supposed to acknowledge the message back to slack. Until you do, it’s hanging, and you can’t duplicate it.
will google that… but had no clue… thanks
but as I siad, it’s interesting how the thing happens on the aws side… like my lambda function
but will check it anyway
based on this, the ack is any response back, no?!
nothing very specific… in which case, I am sending that
that’s why i was confused since, again, it looks like the problem is not on the slack side, since is my lambda that is not processing the functions when it gets the same command
for example my code is like:
...
...
function2()
def function2():
...
...
handler():
print("something")
function1()```
so when sending the command for the first time… everything runs… when sending the same command again, not changing any parameter, the handler starts… but doesn’t invoke function1 and function2
I can see that on cloudwatch logs… saying that the lambda started… but didn’t run… no errors either
That is very interesting. I would be very interested to hear how you solve it. I would add a ton more debugging to the lambda like at each line