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 SamBBest answer by SamB

That’s great to hear, ​@mikem-coalesce! I just checked the bug report again and it’s officially closed! 🎉

In case anyone missed the email notification that was sent, here’s what you need to know:

We want to inform you about an incident that occurred on Tuesday, February 11th, from 22:06 UTC to February 12th, 02:08 UTC. For approximately four hours, incoming Slack New Mention triggers were disrupted for users who had "Trigger for Bot Messages" set to false. As a result, trigger events during this period were not received or processed.

Unfortunately, the affected trigger events cannot be replayed. You may have noticed a higher-than-expected number of errors in your Zap’s task history. While these errors were part of the issue, they do not directly correspond to the actual number of missed mention events during the outage.

We also want to reassure you that these task errors will not count toward your task usage. The issue has now been fully resolved, and your Zaps should be functioning as expected.

Really glad the team was able to get this fixed for you all! If you run into any further issues, feel free to reach out.

In the meantime, happy Zapping! 😁⚡ 

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

6 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
  • 7304 replies
  • 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


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

That’s great to hear, ​@mikem-coalesce! I just checked the bug report again and it’s officially closed! 🎉

In case anyone missed the email notification that was sent, here’s what you need to know:

We want to inform you about an incident that occurred on Tuesday, February 11th, from 22:06 UTC to February 12th, 02:08 UTC. For approximately four hours, incoming Slack New Mention triggers were disrupted for users who had "Trigger for Bot Messages" set to false. As a result, trigger events during this period were not received or processed.

Unfortunately, the affected trigger events cannot be replayed. You may have noticed a higher-than-expected number of errors in your Zap’s task history. While these errors were part of the issue, they do not directly correspond to the actual number of missed mention events during the outage.

We also want to reassure you that these task errors will not count toward your task usage. The issue has now been fully resolved, and your Zaps should be functioning as expected.

Really glad the team was able to get this fixed for you all! If you run into any further issues, feel free to reach out.

In the meantime, happy Zapping! 😁⚡