Trouble with "New Reaction Added" trigger not retrieving data in Zap

Hi ​@bell,

Welcome to the Community.

If you're having trouble retrieving test data with the "New Reaction Added" trigger in Zapier, start by ensuring the connected app (like Slack) has the necessary permissions and access. Verify recent reaction activity, manually add a new reaction to test, and double-check your Zap's configuration to ensure it's monitoring the correct channel. Also, review Zapier's status page for service issues, and consider reconnecting the app. If problems persist, contacting Zapier Support may be the best next step.

If you have any further questions or need more detailed guidance, feel free to ask. We're here to help.

Thank you. I tried what you suggested, but unfortunately, it didn't work. It seems that Zapier is not recognizing the reactions in Slack. What should I do next?!--endfragment>!--startfragment>

Hi there ​@bell,

It looks like the behavior you’re encountering was a known bug. However, this bug has already been fixed. Could you please try to send a new message in Slack and react to it? After that, please go to your Zap and try loading a new sample data.

I'll be keeping an eye out for your response!

Sorry to hear that you’re still running into some trouble with the New Reaction Added trigger, ​@bell. And hope you don’t mind me jumping in here to lend a hand! 🙂

I did some checking and found a recently reported bug where that trigger is not running for reactions added in private channels. Are the reactions being added in a Private Slack channel? Let me know whether that’s the case and I’ll get you added to the bug report so we can notify you once it’s resolved.

Looking forward to hearing from you!

Yes - ours is not working as well, and it’s for private channels.

This is also happening to my team as well. 

our zap worked fine on our private channel for months and is now no longer working. even making the zap from scratch, i am unable to retrieve any data for testing. can I please be added to the bug report as well?

Hi ​@TSC_admin and ​@LZIntegrations. 👋

Sorry to hear that you’re both running into that issue. You’ve both been added to the list of folks being affected by that bug now. I can’t give any sort of estimate as to when it will be resolved, but you’ll definitely get an automatic email notification from us as soon as it is. There’s no reported workarounds at present but I’ll be sure to share details of any I come across in the meantime.

​@bell - keen to know whether your Zap is looking for reactions in private or public channels. Will be keeping an eye out for your reply! 🙂

​@SamB 
Hello from Japan!

My team is experiencing the exact same issue. We have multiple Zaps that are triggered by reactions, and they are all failing to run.

So far, we've confirmed that this is happening within private channels.

(Just to be sure, I will also check with other members to see if all the non-functioning Zaps are related to private channels.)

From my investigation, it seems the following post also describes the same phenomenon, leading me to believe that this isn't an issue affecting only specific users

I believe this is a bug affecting everyone, and for us, this issue is causing significant delays in many of our operations, which is very problematic.

We understand you are busy, but we would greatly appreciate a swift resolution.

Thank you as always🙂

Hey ​@SamB, Could you please add me to the list as well?  

Same here. Keen to be added to the list ​@SamB 

Hi ​@ken.a ,

All good here. Thanks to the team!

Hey everyone! 👋

That’s great news, ​@pierremous! Thanks so much for confirming it has been resolved on your side as well 🤗

Really appreciate everyone’s patience here. I’ll mark Ken’s reply as the best answer here and close this thread now as the issue has been sorted now! 🎉

That said, do keep an eye on things and if you run into any more trouble, please start a new topic in the Community here or contact Support directly to let us know. 

In the meantime, happy Zapping! ⚡