Skip to main content
Question

Error while hydrating data from Slack: Error from Slack: message_not_found

  • May 11, 2025
  • 8 replies
  • 176 views

All of my Slack → Jira Cloud integration Zaps in the past few days (starting May 8) are failing with the below error, but nothing changed on our end.

It’s failing on the issue creation step in Jira with the following error: 

 

I’ve also noticed that the zap was run successfully and also failing at the same time. 

 

 

Do you know why this might be happening, and if there’s anything I can do to resolve it? The integration seems to be working, but I keep getting emails about it, and it’s a bit tedious to keep double-checking whether it actually ran successfully.

 

Thanks so much!

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

8 replies

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • 34072 replies
  • May 11, 2025

Hi ​@csari 

For us to have more info about the error, post screenshots showing how Zap step 2 is configured in the CONFIGURE tab with the field mappings visible.

 


  • Author
  • Beginner
  • 1 reply
  • May 12, 2025

Hi ​@Troy Tessalone

This is how the Step 2 is configured: 

 


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • 34072 replies
  • May 12, 2025

@csari 

Things to check/try:

  • Make sure all required fields have values
  • Compare successful VS unsuccessful Zap Runs to see if you can identify the difference that is causing the error
  • Feedback from AI
    •  


  • Beginner
  • 4 replies
  • May 14, 2025

+1 - I have exactly the same issue on all my Slack Zaps. They’re working 90% of runs, but hitting lots of failures with the error ‘This Slack step hit an error
Error while hydrating data from Slack: Error from Slack: message_not_found’ 

 

Has Slack changed its API config somehow?


  • Beginner
  • 4 replies
  • May 14, 2025

Here’s what the log looks like when I try to rerun it: 

 

 


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • 34072 replies
  • May 14, 2025

@csari and ​@Zeus 

Zap trigger: Slack - New Message Posted to Private Channel

This is an instant Zap trigger type that fires from a webhook sent from Slack.

The webhook data payload often only contains a subset of information about the Slack message and that is to be paired with a Slack API call to get the full message info.

The Slack Zap trigger is configured to do that API request behind the scenes.

For the Zap Run errors:

  • there’s a chance that the message was deleted so the Zap triggered to run from the webhook, then could not find the message when attempting to do the API request
  • there’s a chance that the message in the private channel is not accessible by the connected app account using the Slack API request

 


  • New
  • 3 replies
  • May 22, 2025

You should update your slack connection to the latest version. I observed the same issue and it solved the problem


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 9736 replies
  • June 17, 2025

Hey ​@csari and ​@Zeus 👋

Just checking in—were you able to resolve those “Error while hydrating data from Slack: message_not_found” errors in the end? Did Thomas LT’s suggestion to updating the Slack app, or any of Troy’s suggestions, help? Let us know how it’s going, want to make sure this got sorted!