Hello there!
My organization recently started using Pipedream.
However, I am facing read ECONNRESET error almost every time I trigger a workflow.
It even happens from the one step try or the Python sample code(using requests) provided from Pipedream.
I have recreated workflows many times, however, it happens at the end.
Since it happens from the trigger sometime, I cannot even use Pipedream for the automation.
Hope somebody can help me.
Thank you in advance!
Hello @jacoblee, may I ask what specific trigger you’re using? Is it HTTP Trigger?
@vunguyenhung That is a Slack trigger which is triggered when a specific keyword is detected in a specific channel! (But funny thing is the trigger works in edit mode)
Hello @jacoblee, I’ve tested the Slack - New mention trigger and see an issue. I’ve created a Github issue here to track it and put it to Pipedream prioritized component backlog! Our component dev will take a look at it soon!
@vunguyenhung Thank you for taking care of it quickly, and I saw that the ticket was moved forward to done status.
Therefore, I went to Pipedream to re-run my workflow, however, it still seems not working.
I also have seen the recent thread saying Python script is not working with ECONNRESET error which happens to me all the time.
I am not sure if the workflow will be working even the trigger works and also wondering if there is a defect for the whole workflow with some system cause.
I think we had different logs when debugging, and I found that Slack trigger actually worked (since I can see logs printed out from source panel).
The issue was the Python script which trims received data from the previous trigger.
@jacoblee, you will need to create a new Slack - New Mention source in order to have the fix.
The Python issue is interesting, I will try to reproduce it with your hint. Thank you
Hi @jacoblee we’re tracking this particular error here:
Please subscribe for future updates and when a fix is released.
Thanks for your patience!
