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.

Hi, I set up a Zap in January 2022 to pull new items from an RSS feed (this is the trigger) and email them using Gmail.  It was working fine until somewhere between 14th May 2023 and 29th May 2023.  And since then the ‘New Item in Feed in RSS by Zapier’ trigger gives this error in the Zap:

Unable to pull new item in feeds

Please reload the page. If the issue persists, troubleshoot error or contact Support.

Error code: Error while retrieving: The app returned "Not Acceptable".


I have tested the feed with several RSS validators both initially when setting up, at the time of breakage (end of May) and today, and they all say the RSS/Atom feed is valid.  So what is going on?  I made no changes to the Zap to break it, and I don’t think the RSS feed publisher did either, and it certainly still passes RSS validation and looks OK when viewed with curl or a web browser.  Any ideas?  Did Zapier change their RSS feed trigger and break it?

The RSS feed URL is:

https://mume.org/Import/news/rss

I’ve tested the RSS feed today with these 3 validators:

https://www.rssboard.org/rss-validator/check.cgi?url=https%3A%2F%2Fmume.org%2FImport%2Fnews%2Frss

https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fmume.org%2FImport%2Fnews%2Frss

https://www.castfeedvalidator.com/validate.php?url=https://mume.org/Import/news/rss

Hi @Finwe from MUME 

Good question.

Did you review the help article to see if that provides guidance?

https://help.zapier.com/hc/en-us/articles/8495968498957-Common-Problems-with-RSS

 

If you suspect there is an issue, then try opening a ticket with Zapier Support: https://zapier.com/app/get-help

Hi @Finwe from MUME 

Good question.

Did you review the help article to see if that provides guidance?

https://help.zapier.com/hc/en-us/articles/8495968498957-Common-Problems-with-RSS

Thank you for sharing this, but it does not provide any guidance.

If you suspect there is an issue, then try opening a ticket with Zapier Support: https://zapier.com/app/get-help

I actually did open a ticket with Zapier Support back on June 2nd and they said:

We have chosen to make Zapier a self-service product to serve our customers best. This means our customers set up their own workflows, and we stick to asynchronous email support to ensure we can help all of our customers and keep our plan prices affordable.
 
You might want to check out our global user Community (https://community.zapier.com/) to connect with other users and Zapier experts for additional workflow ideas and app recommendations. A good place to start is to ask the community for suggestions or to get inspired by workflows built by other members. Hope to see you there!

Also, I think it broke on May 27th if that helps anyone!

OK, with some help from the server administrator I was able to get the full HTTP headers that Zapier was sending:

GET /Import/news/rss HTTP/1.1|Host:mume.org|sentry-trace:1e1114b6c9f24d71a75604a05e8021c8-9ef3338532fc0699-0|User-Agent:Zapier|Accept-Encoding:gzip, deflate|Accept:text/xml, application/xml, application/rss+xml, application/atom+xml|Connection:keep-alive|x-datadog-trace-id:3932921621446343857|x-datadog-parent-id:4530702252462936352|x-datadog-sampling-priority:-1

And I was able to reproduce the problem with

$ curl -I -X GET https://mume.org/Import/news/rss -H 'Accept:text/xml, application/xml, application/rss+xml, application/atom+xml'
HTTP/2 406
date: Thu, 02 Nov 2023 22:35:14 GMT
server: Apache/2.4.41 (Ubuntu)
strict-transport-security: max-age=15552000
alternates: {"rss.php" 1 {type text/html}}
vary: negotiate
tcn: list
content-length: 411
content-type: text/html; charset=iso-8859-1

Now that we knew exactly where the problem lay, the server administrator was able to change their Apache config to resolve this.

Reply


Terms & Conditions