Why am I Getting a Timeout on a Trigger Despite Only Catching a Payload and Time Set to 120sec?

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

Hey, I am getting a timeout on a trigger, which is super weird as its just catching a payload. time is set to 120sec. any ideas?

That’s just a quirk in the UI that we need to address. When the workflow times out we don’t actually know which step specifically timed out, since the entire lambda execution failed.

I see, seems to be working on respool now. might be the partner then as they are playing aroudn with their API a little bit. cheers

You aren’t the first one to get tripped up by that. I think the team was looking at figuring out a better visual approach for making that clearer.

probably not the last either.