Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

All of my Slack → Jira Cloud integration Zaps in the past few days (starting May 😎 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!

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.

 

Hi ​@Troy Tessalone, 

This is how the Step 2 is configured: 

 

​@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

    •  

+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?

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

 

 

​@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

 

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

Reply


Terms & Conditions