RSS by Zapier trigger partner failure: The app returned "Forbidden"

  • 3 June 2023
  • 1 reply

We have a few long-running zaps using RSS by Zapier to publish items to Facebook pages and Twitter accounts. For the past three days, they have returned the following error: Trigger partner failure: The app returned "Forbidden"." These continue until the zap is eventually paused by Zapier.

I’ve tested each step/action in the zaps without issue, and even re-created and re-tested the zaps from scratch. They will publish social media posts from RSS by Zapier with manual tests, but once the zaps are published and left to run on their own, they return the same error. 

The AI chat says this type of error is often temporary, but this has been going on for three days now. Our other zaps that post to social media but do not use RSS by Zapier appear to work without issue.

1 reply

Userlevel 7
Badge +6

Hi there @eric_c,

Welcome to the Community! 🎉

I looked into this, and it seems like you have already contacted our Support team regarding this issue. Here’s their latest response:

Thanks for writing in to our team! I see that you're looking for some help understanding why the RSS by Zapier app has suddenly started returning "Forbidden" errors and failing to run. I'm sorry to hear about the trouble and will do my absolute best to help here.

Taking a peek at the Zap system logs, I see what you mean about the Forbidden error showing up for all of our recent polling attempts. The high error ratio it's running into is what causes the Zap to be turned off. It's definitely strange to see this, especially with such a sudden uptick.

Stepping back to view your overall Zap dashboard, I see you have a number of Zaps with RSS by Zapier triggers. Of those, four are still turned on. Can you please let me know if you've received any error alerts about those (as a comparison)?

Can you please also give me the date and timestamp of the first error you received? I'd like to check that against other system reports to see if there's a pattern happening. 

I recommend continuing the conversation with one of our Support specialist. They will be able to examine the Zap and its logs more closely in order to identify the underlying cause of the issue.

Thank you for your understanding!