Workflows constantly (and unreliably) timeout

Help
1

I have a cron-tab-triggered workflow which does a fair share of http requests.
Once in every week or so it timeouts, and I can’t seem to find a reason why.

The logs are not helpful:

image
image1132×202 4.44 KB

And every time I manually retry (per the Run Now trigger button), it runs with no error.

I (crudely) placed a few stopwatches to try and debug where it timeouts (if it is within my code), but they don’t ever seem to be reached - the data store is not updated.

image
image1093×140 6.01 KB

I realize this topic might be related to Cron scheduler seems to throw a timeout - #4 by pierce, but I don’t have any manual retries.

2

Hi @ericwu91,

I’m sorry to hear that you’re experiencing timeouts with your cron-triggered workflow. To help you troubleshoot the issue, I recommend checking the following:

  1. Make sure you’re not exceeding the rate limit for cron jobs, which is no more than twice a minute. If you encounter a rate limit error, wait one minute and try again.

  2. Inspect the execution logs for any errors or issues. You can find these logs in the Inspector. Click on any line in the Inspector to view the details of a specific run.

  3. Check the logs for each code step in your workflow. If you’re using console.log() or other functions that print output, the logs should appear directly below the step where the code ran.

  4. If you’re making HTTP requests in your workflow, ensure you’re using the axios constructor from the @pipedream/platform package. This helps manage timeouts and retries more effectively.

If you’re still experiencing issues after checking these points, please don’t hesitate to visit https://pipedream.com/support for more support options.
I’m a bot powered by Pipedream and GPT-4. I’m still learning, so please double check my answers and code! Learn how to build your own.

3

Thanks, @pi . (cute!)

  1. They are not. The cron is configured as once-a-day, every day.
  2. They are not specific.
  3. They seem not to be reached.
  4. I’m using @pipedream/platform 's axios whenever possible; Not always, though.
4

Hi @ericwu91! Have you tried raising your workflow timeout settings to 1min or more? Since it makes many (sync?) HTTP requests, the total time for each one adds up

5

I have not, since I’m on a free plan; Still, the timeouts don’t seem to happen within the code. I’ve placed a few stopwatches to measure each of the (async) http requests, but they aren’t even ever reached.

6

Would you mind raising to see if that’s the issue?
The default timeout is 30s, the free plan allows for up to 5min. If the workflow doesn’t finish execution of all steps, it raises the error

7

You’re correct. I raised the timeout to 300s.
I’ll check to see if I still get timeout errors.

Thanks for now.

1 Like