This topic was automatically generated from Slack. You can find the original thread here.
, I have a workflow where I get a message that it ran successfully in 0 ms, without any errors. However, the workflow is not executing any step, just the trigger. Can you help me?
I’m sorry to hear that you’re having trouble with your workflow. To better assist you, can you please provide more information about the trigger and steps in your workflow? This will help me understand the issue and provide a solution.
I have a trigger of type “HTTP Request”. The next step is code in Node.JS.
When I run this workflow manually using the trigger content for testing, the steps run normally. When this workflow is executed automatically through the trigger, the following steps are not executed.
I use this same trigger and the same Node.JS code in another workflow and the other workflow is working normally
It’s strange that the workflow is not executing the steps when triggered automatically. To help diagnose the issue, please check the following: 1. Make sure the HTTP request sent to the workflow trigger URL is correct and contains the necessary data. 2. Compare the configurations of the working and non-working workflows to see if there are any differences. 3. Check the event history of the non-working workflow to see if there are any errors or unexpected behavior in the logs. If you’re still having trouble, please share more details about the Node.js code and any differences between the two workflows. This will help me provide more specific guidance.
there are no differences between the steps of workflows that work and what doesn’t. So much so that the workflow that does not work does not return any error, it just displays a successful execution time of 0 ms while the other workflows display a execution time of 56,874 ms
It’s unusual for a workflow to show a successful execution time of 0 ms when it’s not executing any steps. To further investigate this issue, please follow these steps: 1. Double-check the trigger settings and ensure that the HTTP request is being sent to the correct trigger URL. 2. Inspect the event history for both the working and non-working workflows to see if there are any differences in the incoming events or execution logs. 3. Make sure that there are no conditional statements or other logic in the Node.js code that might be preventing the execution of the steps in the non-working workflow. If you’re still unable to identify the issue, please consider reaching out to Pipedream support at https://pipedream.com/support for further assistance.