Why is the Timeout Occurring Before the Execution of the Next Block in My Workflow Triggered by an Email?

Help
1

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

Hello, can someone help me understand this timeout issue? I may just not be understanding the UX properly…

I have a workflow triggered by an email that contains a submission ID (i.e. for Jotform). The next step is a bash block that uses the Jotform API to pull the submission data.

In the screenshot below: it looks like the trigger is received and the data is properly captured from it and then the timeout happens before (?) attempted execution of the next block that makes the API call?

I.e. I would expect to see the second step to be where the timeout occurred?

image.png
image.png2094×784 117 KB

2

Yea it’s unfortunately just not great UX. That’s just indicating that the workflow timed out somewhere. The best way to troubleshoot is to just start increasing the timeout and trying to replay that event.

3

Got it thanks. Another question – when replaying – does it actually run the workflow (i.e. actually API calls would be made), or is it just a simulation of what happened?

4

It makes API calls

5

Got it, thanks! So it’s more like a retry rather than necessarily an exact replay/log of what happened.

6

It runs the currently deployed version of the workflow using the original event from that instance (called a “trace”)

7

But yea I think you get it