It could be a couple of things, maybe the workflow is crashing due to a memory limitation if there is a lot of data or the more likely cause is your workflow is timing out as I think there is a limit on the execution time with cloud.
Hi @Jon - the workflow here completes as does a shorter version.
It would seem as long as the workflow completes in under a minute, the Gateway Timeout is absent.
If this workflow was isolated to n8n.io there would be no issue. The challenge is that it’s suppose to send the response back and by the time it does, the timeout error has occurred.
I’m honestly not sure if this is an n8n issue or the caller. Most of the posts on here are about self-hosted or desktop version of n8n. I have it on your cloud version, so those posts didn’t seem relevant.