Thanks for sharing your findings here, @bwtobias!

Hope you don’t mind but I’ve split your comment here out into a separate topic so that we can track users that are having issues with triggering from saved Private messages/DMs here. There’s no ETA on when this will be resolved but we’ll be sure to reach out here with any updates. And we’ll email you as soon as it’s been fixed. 

@cesarabeid and @hduran - am I right in thinking that it’s Private messages/DMs that you’re unable to trigger your Zaps from? Let me know if so and I’ll get you both added to the new bug report.

Look forward to hearing from you! 

So far it seems DM’s are for the most part working just fine for me. I was receiving some 502 errors, but I thought maybe it was just my Todoist connection. I’m testing fine with public channels, private channels and DMs just fine.

That’s very interesting @petethezapper, thanks for letting us know!

Hmm, the bug report is still open but I do know that it’s being worked on so perhaps they’ve implemented a potential fix here?

If not, it could be that there’s some differences in the types of DMs that are triggering and those that aren’t. I wonder if timing is a factor? Perhaps it’s only triggering for saved DMs that are saved within a certain time frame? 

At any rate, we’ll be sure to keep y’all in the loop on any news here. 

DMs are working for me just fine @joelgascoigne looks like you were having the same issue with saves (dunno if that was for DMs or not tho), how are you looking on DMs?

FYI - Everything is working fine for me again with the Save for Later button.

hey there. curious whether or not this bug is still open? A bit confused based on the comments and looking to reactivate the zap that had broken a couple months ago

Hey there, @Zimari - thanks for reaching out. 

I double checked and it looks like this bug is still open though this thread is specifically for messages saved in DM’s. Definitely feel free to turn the zap back on though as everything else should be working now! Just keep in mind DM’s may not be triggering. 

I hope that helps!

Is this broken again? Just started getting these errors today:

Error while hydrating data from Slack: This is a new feature! To take advantage of it, you'll need to reconnect your auth. Requires scope `im:read`. This error could also be generated because you are trying to pull objects (Mention, Reaction, etc) from a D

I went through and reconnected my Slack, still doesn’t work with DMs. Works fine with channels.

Hi ​@petethezapper! 

Thanks for flagging this! I did some checking on this end and spotted that yesterday a new bug report was opened up as this issue appears to have as resurfaced. I’ve gone ahead and added you to the bug report so we can notify you via email as soon as it’s been sorted.

If anyone else in this thread is running into this again as well, let me know and I’ll get you added.

Really sorry this issue has popped up again. The team are looking into resolving this as quickly as possible but do reach back out here if there’s anything else I can help with in the meantime. 

Hi folks, just following up here to confirm that the bug has been resolved! 

Thanks so much for your patience on this. If you’re still experiencing any issues please do reach out in the Community or get in touch with the Support team to let us know. In the meantime, happy Zapping!