However, the actual workflow doesn’t send anything to my Discord Webhook listener. If I click on Send Test Event, I do see a message being posted through my Discord Webhook listener so I know the post.request is working. So why are new events not triggering the post.request?
Hi @rabvigil , thanks for reaching out. Would you mind clicking the Share button in the top-right of the workflow and share it with dylan@pipedream.com? I’d like to take a look at the configuration on our end to see if I can help.
Thanks. I reset the connection between your RSS event source and the workflow. Let me know if you see new events trigger the workflow automatically, as the RSS source finds new items. If that still fails, we can look into it more.
All I did in this case was to toggle the trigger step off and on again (in the top-right of the trigger). If that fails, you can try deleting the trigger step (x in the right corner) and adding the source anew.
I’ve noticed that this issue — where it looks like the trigger is on, when it is not — has happened to other users, so hopefully we can find the conditions under which it occurs and fix the bug so it’s no longer an issue in the future!
I see, I will keep an eye on it then. This was just a test, but the real Workflow that I am using reads an anchor rss for a weekly podcast update. So I can only test the “real one” once a week.
@hexlet I also made some modifications to the original workflow, so please try triggering that one again (add a row to Google Sheets), if you don’t mind - I’d like to see if that worked.
And we have several workflow that sometime doesn’t work. Can you tell what the global problem is and how we can solve it without involving you every time? And how to be sure that at some point the events will not be missed, because in such a large number of events, you can easily lose several?
@hexlet we did end up processing the event, just a couple of hours late (we’re looking into this separately). Notice that you have two events from 4:49 in your workflow. The top 4:49 event was actually triggered from the 2:35 event from the source. The system that handled the workflow delivery had a hiccup around 2:35, which is why the event wasn’t immediately delivered, and then the next time the workflow triggered at 4:49, we picked up both events.
We’ll keep looking into this on our end to find the source of the original hiccup, but hope that helps.
@hexlet I can see that some events failed to trigger your workflow, but too much time has passed for me to troubleshoot why. I can tell you that the connection between your source and workflow is currently active. Could you try adding a test row to the source Google sheet and confirm that now works?
No mistake on your end. I simply reset the connection between your trigger and workflow. We’re investigating a potential bug related to this so I appreciate you letting us know about the issue.