Skip to main content
Best answer

Error: This Slack (1.3.7) step hit an error Error while hydrating data from Slack


All of my Slack integration Zaps are failing with the below error, but nothing changed on our end. Is this a new issue and if so, anything I can do to resolve it?

 

This Slack (1.3.7) step hit an error

Error while hydrating data from Slack (1.3.7): isNormalBotMessage is not a function

 

 

Best answer by SamB

Hi there ​@mikem-coalesce, ​@FF Automations and ​@adaminproduction! 👋

I’m so sorry you’re all running into these errors. I looked into this and found that a bug report was opened earlier today for those “Error while hydrating data from Slack: isNormalBotMessage is not a function” errors on Slack’s New Mention trigger.

I can’t give any estimate on when it will be fixed but I’ve added you all to the list of affected users, so you’ll receive an email update as soon as it’s resolved. Really appreciate everyone’s patience, and I’ll follow up here with any updates in the meantime!

View original
Did this topic help you find an answer to your question?

5 replies

Same issue on my end! 
 

 


I”m getting exactly the same error and it’s happening at the same time - I was looking through previous tabs and they say they fixed the bug but i’m getting hundreds of automations stopped


guess I’m glad I’m not the only one...


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 7289 replies
  • Answer
  • February 12, 2025

Hi there ​@mikem-coalesce, ​@FF Automations and ​@adaminproduction! 👋

I’m so sorry you’re all running into these errors. I looked into this and found that a bug report was opened earlier today for those “Error while hydrating data from Slack: isNormalBotMessage is not a function” errors on Slack’s New Mention trigger.

I can’t give any estimate on when it will be fixed but I’ve added you all to the list of affected users, so you’ll receive an email update as soon as it’s resolved. Really appreciate everyone’s patience, and I’ll follow up here with any updates in the meantime!


@SamB thanks, it does seem to be working now