Skip to main content

Starting at 8:45am this morning multiple Zaps that have had no changes to them in months and whose tested connections are all still valid and passing have started giving me “Error From Slack: Fatal Error” 

not sure what could suddenly be causing it? I’m seeing a weird variable associated with one of our picklist fields but the field hasn’t been changed in SFDC in over a year and the connected user has full access to it

 

This post has been edited by a moderator to remove personally identifiable information (PII). Please remember that this is a public forum and avoid sharing sensitive details.

Looks like Slack could be experiencing some issues…
 

 


Hi ​@Jchrist Envoy, welcome to the Community! 👋

Yes, you’re right—I looked into it, and seems those errors are related to that recent Slack incident. While yesterday’s incident appears to have been resolved, there’s still an ongoing incident that could be contributing to these errors. I’d recommend keeping an eye on their status page to stay updated on the situation. 

Once Slack fully resolves the issue, you should be able to successfully replay any Zap runs that had those “Error From Slack: Fatal Error” errors. 

Hopefully they’ll have it sorted soon! Let me know if there’s anything else I can help with in the meantime. 🙂


Thanks ​@SamB , I reran all the failed Zap Runs yesterday after our org’s Slack appeared to begin functioning and everything is working as expected


Yay! That’s great news, ​@Jchrist Envoy. Thanks so much for following up to confirm it’s working again. 🎉

If anything else comes up, feel free to reach out. In the meantime, happy Zapping! ⚡