Why is there a Timeout Error Report in PD Workflow Trigger and Why is No Step Highlighted?

1

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

I got a timeout error report on a PD workflow. I click to see it… and it timed out in the trigger, that can’t be right, can it? This same workflow has an earlier event where a step timed out and it’s clearly shown (step 3 of 3), but in this case, no step is highlighted, and its just a red banner about the timeout

2

Ah yeah, that probably means it’s a memory error if no steps executed

3

See this thread

4

but the error msg said, “You’ve exceeded the default timeout for this workflow. You can raise the timeout in your workflow’s Settings. See Troubleshooting Common Issues - Pipedream”

5

Yes, we can’t reliably assume it’s a memory error from the AWS error messages, it’s a known gap

6

Could you try increasing the memory and see if it helps?

7

sure - but the error’s not consistent :slightly_smiling_face:

8

done

9

Seeing the executed steps and the memory usage before the crash would really help…

10

according to thee xecution, it stopped at trigger

11

not sure where id see the memory usage

12

Yeah that’s not right.

13

It executed stuff, but you can’t see it.

14

yeah, big paste -

15

image.png
image.png1719×823 69.1 KB

16

Yup, same as usual.

17

But it’d be helpful to see:
• Step 1 - memory usage: 94/256MB
• Step 2 - memory usage: 234/256MB
• Step 3 - TIMEOUT or OOM.

18

Then we’d know to increase the memory, and that step 2 obviously has some kind of problem.

19

so i may be missing it, but where is that in the UI?

20

It doesn’t exist