Slack Reaction trigger no longer works

​Welcome to the community, ​@M.E.Kim—great to have you here! 😁

Sorry to hear of the troubles with the Slack New Reaction Added trigger. It’s very strange that it’s working for the older Zaps but not the newer Zaps. Are the old Zaps that are working using an older version of the Slack app by any chance? If they are they’ll likely have a version number next to their name e.g. “(1.3.11)” or say “(legacy)”. 

If that’s the case, then it could be that there’s a bug with the latest version of the Slack trigger. 🤔 So I’d suggest contacting our Support team here so that they can investigate it further. They’ll be able to confirm if it is indeed a bug and can get a bug report opened so our engineers can get it fixed.

Can you make a copy of an older Zap that is working and edit it to match the settings of one of the newer Zaps that isn’t working, to see if it triggers? If it does then you can use that approach to workaround the issue in the meantime. 

Looking forward to hearing from you!

Hi @SamB,

Thanks for the reply!

I don’t see “(legacy)” in the Zap that’s currently running w/o any issues. Though, when I duplicate the zap and try to test the trigger, it doesn’t output any results, which makes me wondering why the zap that’s currently running works just fine.

I’ll contact the support team, thank you!

You’re welcome, ​@M.E.Kim! 😊 I’m sorry it didn’t work as I’d hoped. Hopefully the Support team can get to the bottom of it quickly. 🤞

Please keep us posted on what they find—I’d love to know what’s causing this!

Hello,

Unfortunately we are observing the same problem since saturday (10:45 UTC+1 => still working).

Updating to latest zap version of this trigger doesn’t change anything.

Strangely we can see datas in “records” in the “test” step of zaps but it doesn’t actually trigger the zap (nothing in the history)

Just reported that to the support as it is highly problematic for our company

FYI, Problem solved a few minutes ago and communicated by the support team

Thanks so much for letting us know, ​@Thomas LT! 🤗 So glad the Support team were able to help and the issue has since been fixed.

​@M.E.Kim, are things working on your end as well now? 🤞

We’re still having a trouble getting the test trigger work, but I’m in contact with the support team. I’ll update once things are resolved!

Thanks ​@M.E.Kim, hopefully the Support team can help get things sorted for you soon!

Thanks! 

Unfortunately, I think this is like the third time they changed the person from Support team, asking me providing the same information over and over again. :cry:

Maybe this is not  fixable? I’m not sure if this is affecting our Zaps only though…because still we can’t create a new zap or update an existing zap, to get the test trigger results by slack reaction, if we don’t specify specific user name & emoji name.

That sounds really frustrating, ​@M.E.Kim—I’m so sorry you’ve had to repeat everything to different support reps. I had a look at the support ticket and it appears they since identified that you’re running into a bug. We aren’t able to give any sort of ETA on when it will be fixed but we’ll definitely send an email notification once it is!

As a workaround, they suggested using custom pill mapping to select any fields that are missing from the test record. I’ll share the details on that here in case it’s helpful for anyone else coming across the thread:

Hope that helps. Let us know if you have any questions or if there’s anything else you need help with in the meantime.