Why Did My Slack App Crash and Stop Detecting Events or Listing Channels Despite Reconnecting?

This topic was automatically generated from Slack. You can find the original thread here.

My Slack app completely crashed.
It’s no longer detecting events or listing channels while I’m building, and reconnecting hasn’t fixed it.
What’s happening?

Hi , could you access your Pipedream Sources page, select your source, switch to the LOG tab and show me the screenshot?

I would like to dig deeper into your issue

It just stopped working since 20th Oct.

I’ve tried reconnecting several times, hoping it would solve the issue, but none of them are receiving the webhook after clicking the button on the Block Kit messages.

Hey , sorry for the late reply. I think this may because we recently released Slack V2, which use a different Slack App for Pipedream.

May I ask if you created a brand new sources or recorrect the existing sources? I would recommend you to create a brand new source instead.

I did both

Got it, I’ll try to reproduce and get back to you

Hi , I could NOT reproduce your issue. Here’re my steps:

  1. I setup a new Pipedream source - Slack - New interaction event
  2. Then I send 2 Slack message with interaction events using Pipedream workflow (1st, 2nd, 3rd)
  3. On the Slack message, I click the “Approve” & “Google” & “Bing” button
  4. Then I observed new events on the Pipedream source - Slack - New interaction event (4th image below)

Please note that only messages created via Pipedream’s Send Block Kit Message Action, or via API call from the Pipedream app will emit an interaction event with this trigger.
Block kit messages sent directly via the Slack’s block kit builder will not trigger an interaction event.
See the documentation for more details.

Yeah it was working fine but it hasn’t been since the AWS outage.