I have several zaps that are triggered when a user react on a message in a Slack channel, which used to work fine, and existing zaps are properly triggered.
However, the trigger doesn’t work for the newly created zaps. When I test the trigger, it basically returns nothing even though the reaction event is happened. It only works if I set a specific user. When I leave the User attribute value empty, it doesn’t work.
Is anyone seeing this issue, or any help resolve the issue would be much appreciated, thank you!
Best answer by SamB
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:
As a workaround, if there are fields that are missing because we aren't able to load in a real sample. We can use a custom pill to create the field manually.
Here's a doc that goes into that more:
Hope that helps. Let us know if you have any questions or if there’s anything else you need help with in the meantime.
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.
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.
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.
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:
As a workaround, if there are fields that are missing because we aren't able to load in a real sample. We can use a custom pill to create the field manually.
Here's a doc that goes into that more:
Hope that helps. Let us know if you have any questions or if there’s anything else you need help with in the meantime.
