Any Flow with starts with the RSS Trigger When a feed item is published" fails on the trigger with the below error. Help!
Failed to read requested Feed information. Details: 'Text' is an invalid XmlNodeType. Line 2, position 307. clientRequestId: 0d09a767-c63e-4362-a007-79e70716ef1c
Would you please share the flow configuration i na screenshot?
Just from the error message, the error should be related with file type not match.
" 'Text' is an invalid XmlNodeType. "
The RSS feed only has the RSS feed URL as input, so I don't think the fail is caused by RSS trigger (if it has been well configured).
Here is a bit more information to diagnose issue. Seems to only happen with the Associated Press (AP) RSS feeds
1. "When a feed item is published" RSS Trigger
INPUTS - The RSS feed URL
2. Error: BadRequest
OUTPUTS - Status code 400
"message": "Failed to read requested feed because the content returned is not valid XML format. Details: The element with name 'HTML' and namespace '' is not an allowed feed format.\r\nclientRequestId: 145b2e2f-440f-45c3-9bfc-20bb3d5fe020",
Failed to read requested feed because the content returned is not valid XML format. Details: The element with name 'HTML' and namespace '' is not an allowed feed format. clientRequestId: 145b2e2f-440f-45c3-9bfc-20bb3d5fe020
Headers (if required for debugging):
"Date": "Sun, 20 Aug 2017 14:24:57 GMT",
"Content-Type": "application/json; charset=utf-8",
Issue also occurs with RSS Feed URL: http://hosted.ap.org/lineups/TECHHEADS.rss
Here's a different example, but I'll give more details. Just to recap, for the Associated Press (AP) RSS feeds, Using the below RSS URL, you should be able to easily reproduce. I can also reproduce with other AP News RSS feeds.
1. TRIGGER - "When a feed Item is published"
The RSS feed URL: http://hosted.ap.org/lineups/BUSINESSHEADS.rss
2. ERROR: BadRequest.
"message": "Failed to read requested feed because the content returned is not valid XML format. Details: The element with name 'HTML' and namespace '' is not an allowed feed format.\r\nclientRequestId: 3f362344-2fd3-4f59-b872-ad0df82f90a3",
ONLY ONE STEP, initial trigger with the RSS URL provided above. That's the entirety of the workflow.
When I look at a network trace when requesting that RSS URL using a popular RSS reader, it looks like that AP RSS link is redirecting to an HTML page via a 302 Moved Temporarily response instead of returning RSS XML in the response. That is definitely not compliant with the RSS spec.
It might require specific user agents to get the RSS XML feed or something else about the request, but that is not compliant with the RSS spec.
Here is a terse summary copy of a network trace when using rss feed reader chrome extension:
302 Redirect to http://hosted.ap.org/specials/bluepage.html
Even though the "Accept" request header has a value of "*/*" that means accept all content types, it looks like AP is deciding that it's a browser so it redirects to a browser-friendly HTML page,
I will send a mail over to the team that owns the RssFeedReader connector and see what they say about this one.
It did work using Digg online RSS reader service for me, so Digg must be doing something to ensure it gets RSS XML instead of it thinking it's a browser.
Based on analysis from the feed reader connector team, the .rss URL that you provided is a collection of RSS feeds, customized based on the state/sources you select in the browser, which get saved in the browser cookie. For example
Cookie: SITE=WABEJ; SECTION=HOME
Anyways, you can make this work by selecting the state you want by adding it to the query string :
To figure out the query string, you can also interactively click on the state and source you are interested in a browser, which will redirect you to a URL like this:
This may work, or else replace everything before the ? such as this:
Keep up to date with current events and community announcements in the Power Automate community.
Join us in Las Vegas to experience community, incredible learning opportunities, and connections that will help grow skills, know-how, and more.
Check out the latest Community Blog from the community!