Intermittent Timeout Issues with Pipedream HTTP Request Trigger on Free Plan: Any Suggestions?

Help
1

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

Hi everyone,
i’m actually testing pipedream and i’m on the free plan, actually.
i love pipedream as it’s for me a much much simpler alternative to AWS or even my own hosting :slightly_smiling_face:

i’m actually testing a workflow trigger by a HTTP request.
A thing puzzles me : my workflow works one time out of two : it triggers correctly the first time, and if i call it 1 min after that i have a timeout.
if i trigger it 3 times in a row, first and third times work well, second time goes time out…
And, nothing changes between the 3 times (it’s just trigger by a button click on my front end, and the query parameters are the same).

Any idea about what’s happening ? is it due to free plan limitations ?

Thanks for any help :slight_smile:

2

Hi Guillaume, is it possible your workflow is configured to send an HTTP response? If so you might be having an issue with a step that is exceeding your workflow’s timeout settings.

3

Yes, but the answer seems quite simple though :

image.png
image.png696×236 19.3 KB

4

Yes, simple indeed. And this is the only step in your workflow?

5

Nope. I have a a python script just before.
But when the timeout occurs, the python script doesn’t even run…
(it sends some data through an API call and i never receive the data on this endpoint)

6

(i just have 3 steps : the trigger, the python script and the js response)

7

Have you tried debugging with a print() statement just to sanity check that the Python step does not run? Just curious.

8

Yep. i have plenty of them … but on timeouts, i can’t access them.
Here’s the result with a timed out workflow (screenshot 1) whereas when it works fine (screenshot2)

image.png
image.png1463×977 88.2 KB

image.png
image.png1253×1139 91 KB