@fce803cc @6a75920f so strange.  I’m going to do some more digging with it 

 @fce803cc @6a75920f I even checked for a redirect and it isn’t redirecting 

 @fce803cc @6a75920f however if I put it in my castamatic and subscribe it gets the correct title so the feed is right.  Now to just figure out what is causing it to get the other.  Wait here is a thought it is still wrong in iTunes.  Is the parser checking to see what it is in iTunes 

 @fe436cc6 Do you run the server that this feed hosts from? 

 @fe436cc6 Nevermind, I see that it's on the Blubrry CDN. 

 @fe436cc6 Ok, so check this out.  If I grab the feed in a browser it returns the correct data.  If I, however, grab the feed using Aggrivator (the polling process for the Index) it returns this XML:

https://cdn.masto.host/podcastindexsocial/media_attachments/files/111/138/870/977/979/766/original/a3b203d9ff038aa2.png 

 @fce803cc what the heck. The correct is shown if I pull in postman 

 @fe436cc6 There's caching somewhere.  Trying to find out where and how. 

 @fce803cc ok.  Sounds good.  I can also work with the client to see about caching. But I was working with them yesterday and didn’t see anything about caching 

 @fce803cc so it looks like Podcast index is now right.  They published an episode but did you do anything? 

 @fe436cc6 I did nothing.  This pretty much confirms it was a caching issue since the feed change on the source CDN triggered the correct content to come through.  I see the XML and it's right now. 

 @fce803cc wow.  We’ll thanks for your help on this.  While weee on this podcast can you delete this ID 5951058 it’s a dupe of the official one.  Not sure why blubrry has more than one feed for it but my guess is they podping end on publish and it got added.  Thanks. 

 @fce803cc no this is a blubrry hosted one.  I’m helping them change the name.  The person who set up the feed is no longer at the church.  I think apple podcast is under his iTunes.  So I am going to work with them to get it changed but it isn’t changing in iTunes now. But I wonder if that is due to the last build time