Why RSS trigger takes forever to fetch data?

Help
1

Hello.

I defined this RSS trigger, and it always shows “Waiting for event” loading message

image
image1920×1039 146 KB

2

Hi @slishnevsky,

It seems like you’re experiencing an issue with your RSS trigger not firing as expected. This can happen for a few reasons, so let’s troubleshoot step by step:

  1. Check the RSS Feed URL: Ensure that the URL you are using for the RSS feed is correct and accessible. You can test this by trying to access the URL in a web browser or using a tool like curl to fetch the feed data.

  2. Validate the RSS Feed: Use an RSS feed validator to make sure the feed is valid. You can use the RSS validator at W3C Feed Validation Service, for Atom and RSS to check for any issues that might prevent the feed from being properly read.

  3. Review the Polling Interval: The RSS trigger polls the feed at a set interval. If the interval is set too long, it might seem like it’s always waiting for an event. Consider adjusting the polling interval to a shorter duration if possible.

  4. Inspect for Recent Items: The RSS trigger fires on new items. If there haven’t been new items since the last poll, it will continue to show “Waiting for event”. Ensure there are new items in the feed that have been published after you set up the trigger.

  5. Check Pipedream’s Logs: Go to your Pipedream dashboard and inspect the logs for the workflow. The logs might provide more insight into what’s happening. Look for any errors or messages related to the RSS trigger.

  6. Recreate the Trigger: If none of the above steps work, try recreating the RSS trigger in your workflow. There might have been an issue during the setup process.

If after following these steps you’re still facing issues, I recommend reaching out for more personalized support. You can visit Support - Pipedream for more help.

I’m a bot powered by Pipedream and GPT-4. I’m still learning, so please double-check my answers and code! Learn how to build your own.

3

Could you try adding a new trigger by following these steps:

  • Click on the plus icon to create a new trigger
  • Type in RSS in the search apps field
  • Select New Item in Feed

That will contain the most updated version for the RSS trigger. The one you selected in the new trigger selector is an outdated version, and we’re going to fix that.

Let me know if this works!

4

That’s what I did :slight_smile:
I have several RSS triggers.
This one works: https://news.google.com/rss/search?q=site:twitter.com/oann when:1h
This one doesn’t: https://news.google.com/rss/search?q=site:twitter.com/chanelrion when:1h
This one doesn’t: https://news.google.com/rss/search?q=site:twitter.com/actbrigitte when:1h
This one doesn’t: https://news.google.com/rss/search?q=site:twitter.com/anillarionov when:1h

No events loaded, constantly waiting…

5

Could you please request changes to an existing integration at Support - Pipedream?

  • Head over to Support - Pipedream
  • Click on the “Request an Integration” card.
  • Select “B - Request changes to an existing integration.”

This way, it gets logged in our public repo, and the component development team can be notified.
I believe the code needs to be adapted for search queries.
Thanks!

6

I create a Support request.
But they replied out of context, that my workflow generated an error "ETELEGRAM: 429 Too Many Requests: retry after 5 "

This is not the reason. The issue happened long before I started to run the workflow and still exists.
It actually happens in the workflow during the development stage, before I did any runs.

And I don’t know how to reply to them. Just received a no-reply notification.
Here is the workflow, you can clone it to your workspace and see the problem yourself.

Share link created and copied to clipboard Sign Up - Pipedream

7

Sorry, could you actually report this issue in our public repo?

  1. Head over to Support - Pipedream
  2. Click on the “Request an Integration” card.
    image
    image1028×468 15.6 KB
  3. Select “C - Report a problem with an existing integration.”
    image
    image846×486 34 KB
  4. Fill out the form with details of the issue.

This way, it gets logged in our public repo, and the component development team can be notified.

Thanks,

8

That’s what I did.
Oh, sorry, I selected “Submit a support ticket”.
I will do it now…
DONE.