This topic was automatically generated from Slack. You can find the original thread here.
is there a way to delay a workflow for 10 minutes.
I have a trigger for when a zoom call ends. I want to grab the transcript and manipulate it, but i’m running into an issue because the transcript is not immediately ready.
To delay a workflow for 10 minutes in Pipedream, you can use the built-in Delay actions or the $.flow.delay function in Node.js. Since you have a trigger for when a Zoom call ends and you want to wait for the transcript to be ready, you can insert a delay step in your workflow after the Zoom trigger. Here’s how you can implement a delay: 1. Using the Delay App: - Search for the Delay app from the step menu in your workflow. - Select the Delay Workflow action. - Connect your Delay account. - Set the Duration to delay to 10 minutes. You can specify this as 600,000 milliseconds (since 1 minute = 60,000 milliseconds). 2. Using Node.js Code: - Add a Node.js code step in your workflow. - Use the following code to delay the execution for 10 minutes: ```
export default defineComponent({ async run({ steps, $ }) { // Delay the workflow for 10 minutes (600,000 milliseconds) return $.flow.delay(600000); }, });
would i need to increase my workflow timeout?
To determine if you need to increase your workflow timeout, consider the following: 1. Current Execution Time: Check if your workflow is consistently hitting the default execution time limit. If your workflow is timing out, it might be necessary to increase the timeout. 2. Workflow Complexity: If your workflow involves complex operations, such as processing large datasets or making multiple API calls, it might naturally take longer to execute, necessitating a longer timeout. 3. Expected Execution Time: If you expect your workflow to take longer due to its nature, increasing the timeout can prevent interruptions. If you decide that increasing the timeout is necessary, you can configure a custom timeout in your workflow settings. If you need further assistance or have specific issues, please visit Support - Pipedream for more support options.
Yea the delay step will not impact overall timeout, that’s likely coming from a different step
You can literally delay execution for up to a year
dang that’s pretty cool
Ok so it’s probably just my other nodes taking a bit
I was confused because execution was shown to stop at the pause node
Yea, sadly that’s just poor UX
Understood so assume that the node that failed is the one after the last node shown in the run?
No, we actually don’t have visibility into where the timeout occurred. We package up the entire deployed workflow an run it. If something in there times out, Lambda just throws.
