How to Solve Recurring Timeout Error in Different Steps Despite Successful Individual Testing?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

Hey I keep running into this error, in different steps. But when I test them individually, they work. How can I solve this?

TIMEOUT: TIMEOUT
    at Timeout._onTimeout (file:///var/task/lambda_handler.mjs:921:23)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)
2

I’m sorry to hear that you’re experiencing issues. The error message you’re seeing is a timeout error. This typically happens when a step in your workflow is taking longer than the allowed execution time. In Pipedream, the timeout for HTTP requests made with $.send.http() is 5 seconds. This time includes DNS resolution, connecting to the host, writing the request body, server processing, and reading the response body. If any requests exceed this 5-second limit, a timeout error is thrown. If you’re experiencing this error across different steps, it could be that the cumulative time taken by these steps is exceeding the limit, even if they work individually. To solve this, you might want to look into optimizing your workflow to reduce execution time. This could involve reducing the amount of data being processed, optimizing any loops or recursive functions, or splitting the workflow into smaller, more manageable parts. If you continue to experience issues, please visit https://pipedream.com/support for more support options.

3

can I increase the timeout limit?

4

Yes, you can increase the timeout limit for your workflows in Pipedream. The default execution limit for HTTP and Email-triggered workflows is 30 seconds, and for Cron-triggered workflows, it’s 60 seconds. If your workflow is exceeding these limits, you can increase the timeout limit up to a maximum value set by your plan. For Free tiers, the maximum time per execution is 300 seconds (5 minutes), and for Paid tiers, it’s 750 seconds (12.5 minutes). You can change this limit in your workflow’s settings. Here’s the link to the settings documentation: Settings Please note that if your workflow continues to time out after increasing the limit, it might be a good idea to investigate why your code is taking longer to execute. It could be due to a slow response from a third-party API or processing a large amount of data. If you need further assistance, please visit https://pipedream.com/support for more support options.